Stored script execution via undisclosed rendering path
Published Sep 5, 2025 · Updated Apr 28, 2026
Stored XSS in Sudar Muthu WP Github Gist 0.5 and earlier allows remote authenticated users to inject scripts into site pages. Patchstack identifies contributor access as the gate but does not disclose which input field accepts the payload or which rendering path emits it without neutralization. Execution requires a visitor to view affected content, placing the script in that viewer’s browser context.
Summary
What happened
Stored XSS in Sudar Muthu WP Github Gist 0.5 and earlier allows remote authenticated users to inject scripts into site pages. Patchstack identifies contributor access as the gate but does not disclose which input field accepts the payload or which rendering path emits it without neutralization. Execution requires a visitor to view affected content, placing the script in that viewer’s browser context.
The record
- CVE
- CVE-2025-58875
- Published
- Sep 5, 2025
- Updated
- Apr 28, 2026
- Vendor
- Sudar Muthu
- Product
- WP Github Gist
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 5, 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 <=0.5
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