Stored XSS via unescaped spoofed HTTP header
Published Sep 26, 2024 · Updated Apr 8, 2026
Stored XSS in nitinmaurya12 WordPress Visitors 1.0 and earlier allows remote attackers to inject scripts through a spoofed HTTP header. The plugin stores an attacker-controlled header value without sufficient sanitization and renders it without escaping on the nm_vistior page. No authentication is required to plant the payload; script execution occurs when a user opens that visitor page.
Summary
What happened
Stored XSS in nitinmaurya12 WordPress Visitors 1.0 and earlier allows remote attackers to inject scripts through a spoofed HTTP header. The plugin stores an attacker-controlled header value without sufficient sanitization and renders it without escaping on the nm_vistior page. No authentication is required to plant the payload; script execution occurs when a user opens that visitor page.
The record
- CVE
- CVE-2022-4541
- Published
- Sep 26, 2024
- Updated
- Apr 8, 2026
- Vendor
- nitinmaurya12
- Product
- WordPress Visitors
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo