Contributor-level stored XSS via unescaped input
Published Jan 7, 2025 · Updated May 11, 2026
Stored XSS in hpinfosys Metadata SEO 2.3 and earlier allows remote authenticated users to inject scripts into WordPress pages. Public advisories do not identify the affected field or code path; they state that stored contributor input is insufficiently sanitized and escaped during page generation. Contributor-level access is required to plant the payload, and a later visitor must open the injected page for script execution in that visitor's browser.
Summary
What happened
Stored XSS in hpinfosys Metadata SEO 2.3 and earlier allows remote authenticated users to inject scripts into WordPress pages. Public advisories do not identify the affected field or code path; they state that stored contributor input is insufficiently sanitized and escaped during page generation. Contributor-level access is required to plant the payload, and a later visitor must open the injected page for script execution in that visitor's browser.
The record
- CVE
- CVE-2025-22516
- Published
- Jan 7, 2025
- Updated
- May 11, 2026
- Vendor
- hpinfosys
- Product
- Metadata SEO
- Classifications
- CWE-79, CAPEC-592, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 7, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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 <=2.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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