Contributor-level stored XSS via remaining shortcode
Published Sep 9, 2025 · Updated Apr 28, 2026
Stored XSS in the WordPress ticketing plugin through 2.0.22 allows remote authenticated users to execute scripts through the remaining shortcode. Upstream release notes identify the shortcode as the affected locus but do not disclose which input or output operation lacks neutralization. Contributor access is required to store the payload, which executes when a visitor loads the affected content.
Summary
What happened
Stored XSS in the WordPress ticketing plugin through 2.0.22 allows remote authenticated users to execute scripts through the remaining shortcode. Upstream release notes identify the shortcode as the affected locus but do not disclose which input or output operation lacks neutralization. Contributor access is required to store the payload, which executes when a visitor loads the affected content.
The record
- CVE
- CVE-2025-58988
- Published
- Sep 9, 2025
- Updated
- Apr 28, 2026
- Vendor
- Damion Armentrout
- Product
- My Tickets
- Classifications
- CWE-79, CAPEC-592, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 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.0.22 changes=[{"at":"2.0.23","status":"unaffected"}]
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