Stored XSS via unescaped contributor content
Published Jun 6, 2025 · Updated Apr 28, 2026
Stored XSS in Shahjada WPDM – Premium Packages 6.0.6 and earlier allows remote authenticated users to inject scripts into WordPress pages. The public advisory attributes the flaw to insufficient input sanitization and output escaping but does not identify the affected parameter or function. Contributor access is required, and the stored script executes when another user views an injected page, allowing actions in that user’s browser context.
Summary
What happened
Stored XSS in Shahjada WPDM – Premium Packages 6.0.6 and earlier allows remote authenticated users to inject scripts into WordPress pages. The public advisory attributes the flaw to insufficient input sanitization and output escaping but does not identify the affected parameter or function. Contributor access is required, and the stored script executes when another user views an injected page, allowing actions in that user’s browser context.
The record
- CVE
- CVE-2025-30991
- Published
- Jun 6, 2025
- Updated
- Apr 28, 2026
- Vendor
- Shahjada
- Product
- WPDM – Premium Packages
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 6, 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 <=6.0.6 changes=[{"at":"6.0.7","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