Legal
Security policy.
How to report a vulnerability, and how PublishRank approaches secure development.
Best for
Publishers and researchers reporting a potential vulnerability
Suggested path
Find responsible reporting guidance and practical hardening recommendations.
You will leave with
A safer, focused way to report and investigate security concerns.
Last updated: 1 November 2026
Reporting a vulnerability
If you believe you have found a security issue in the plugin or this website, please tell us privately through the contact form with the topic “Bug report” and the word SECURITY at the start of your message. Do not publish details or open a public issue until we have had a reasonable chance to fix it.
Include the affected version, steps to reproduce and the potential impact. We will review reports in good faith but cannot promise a response time or a reward.
Supported versions
Security fixes target the latest release on GitHub. Please update before reporting.
How the plugin approaches security
PublishRank validates URLs and input, sanitizes settings, escapes frontend output and validates custom HTML and shortcode output. Dashboard configuration is protected by WordPress permissions.
- URL and input validation
- Settings sanitization
- Frontend output escaping
- Custom HTML and shortcode validation
Hardening your site
Keep WordPress, themes and plugins updated, use strong unique passwords and two-factor authentication, and keep backups. Built-in login URL protection and optional request controls reduce noise but do not replace a firewall.
This website
The site is statically served with a server-rendered contact endpoint on Vercel. The contact form is protected by validation, a honeypot field and rate limiting. Never send credentials through it.
A stronger publishing workflow.
Start with the guide. Build a better foundation for every story.