CVE-2026-97341 wp-buy CVE debrief

Who should care

Defenders responsible for WordPress installations with the Visitor Traffic Real Time Statistics plugin should assess exposure and prioritize remediation. This includes reviewing the plugin's version, verifying the presence of the vulnerability, and updating to a version that addresses the issue. Additionally, defenders should consider implementing compensating controls, such as monitoring and detection, to mitigate the risk of exploitation.

Why it matters

The Visitor Traffic Real Time Statistics plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting, allowing unauthenticated attackers to inject arbitrary web scripts. Defenders should prioritize verifying exposure and remediation.

• Unauthenticated attackers can inject arbitrary web scripts in pages
• Injected scripts execute whenever a user accesses an injected page
• Defenders must verify exposure of the plugin in their environment
• Remediation requires updating the plugin to a version that addresses the vulnerability

Technical summary

The Visitor Traffic Real Time Statistics plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via 'X-Real-IP' HTTP Header in all versions up to, and including, 8.16 due to insufficient input sanitization and output escaping. This allows unauthenticated attackers to inject arbitrary web scripts, which can be executed when a user accesses an injected page. The vulnerability is caused by the plugin's failure to properly sanitize and escape user-supplied input from the 'X-Real-IP' HTTP header. This issue affects the plugin's functionality, potentially allowing attackers to compromise the security of WordPress installations.

Defensive priority

Defenders should prioritize verifying exposure of the Visitor Traffic Real Time Statistics plugin in their environment and assess the risk of unauthenticated attackers injecting arbitrary web scripts.

Recommended defensive actions

• Verify exposure of the Visitor Traffic Real Time Statistics plugin in your environment
• Assess the risk of unauthenticated attackers injecting arbitrary web scripts
• Review and update the plugin to a version that addresses the vulnerability
• Implement compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, but the exact versions affected and remediation steps require further verification from the official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.