Unauthenticated stored XSS via post_id form submission
Published Oct 2, 2026 · Updated Oct 2, 2026
Stored XSS in MW WP Form 5.1.7 and earlier allows remote attackers to plant scripts through the post_id form parameter. The form submission path stores attacker-controlled post_id data as post meta without sufficient sanitization, and later rendering fails to escape it. An unauthenticated visitor can obtain the form's CSRF cookie by loading the public form; the script runs when another user opens an injected page.
Summary
What happened
Stored XSS in MW WP Form 5.1.7 and earlier allows remote attackers to plant scripts through the post_id form parameter. The form submission path stores attacker-controlled post_id data as post meta without sufficient sanitization, and later rendering fails to escape it. An unauthenticated visitor can obtain the form's CSRF cookie by loading the public form; the script runs when another user opens an injected page.
The record
- CVE
- CVE-2026-96567
- Published
- Oct 2, 2026
- Updated
- Oct 2, 2026
- Vendor
- 株式会社Webの相談所
- Product
- MW WP Form
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 2, 2026CVE publishedPublication date reported by the CVE source.
- Oct 2, 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 <=5.1.7
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started