What this page helps you verify fast
This hub clusters tracked records for visitor-maps so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin visitor-maps (`visitor-maps`), including severity, CVE references, affected versions, and patch status.
Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.
Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.
This hub clusters tracked records for visitor-maps so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Visitor Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'order' and 'sort_by' parameters in versions up to, and including, 1.5.8.6 due to insufficient inpu...
Sorted by latest disclosure date so newly published issues surface first.
The Visitor Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'order' and 'sort_by' parameters in versions up to, and including, 1.5.8.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers to...