Contributor-level stored XSS via script injection
Published Dec 21, 2025 · Updated Dec 21, 2025
Stored XSS in WP Microdata 1.0 and earlier allows remote authenticated users to inject scripts that execute when visitors view affected pages. Patchstack has not published the affected parameter, code locus, or missing neutralization operation. Contributor access is required to store the payload, and execution requires another user to visit the affected content.
Summary
What happened
Stored XSS in WP Microdata 1.0 and earlier allows remote authenticated users to inject scripts that execute when visitors view affected pages. Patchstack has not published the affected parameter, code locus, or missing neutralization operation. Contributor access is required to store the payload, and execution requires another user to visit the affected content.
The record
- CVE
- CVE-2025-62901
- Published
- Dec 21, 2025
- Updated
- Dec 21, 2025
- Vendor
- Tor Morten Jensen
- Product
- WP Microdata
- Classifications
- CWE-79, CAPEC-592, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 21, 2025CVE publishedPublication date reported by the CVE source.
- Dec 21, 2025Record 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=n/a <=1.0
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