Contributor-level stored XSS via undisclosed input handling
Published Oct 27, 2025 · Updated Oct 27, 2025
Stored cross-site scripting in Builderall for WordPress 3.0.1 and earlier allows remote authenticated users to inject scripts. Patchstack has not disclosed the affected input, code path, or missing neutralization operation that stores the attacker-controlled content. Contributor-level access and a later action by a privileged user are required; the stored payload then runs in that user's browser context.
Summary
What happened
Stored cross-site scripting in Builderall for WordPress 3.0.1 and earlier allows remote authenticated users to inject scripts. Patchstack has not disclosed the affected input, code path, or missing neutralization operation that stores the attacker-controlled content. Contributor-level access and a later action by a privileged user are required; the stored payload then runs in that user's browser context.
The record
- CVE
- CVE-2025-62987
- Published
- Oct 27, 2025
- Updated
- Oct 27, 2025
- Vendor
- Builderall
- Product
- Builderall for WordPress
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 27, 2025CVE publishedPublication date reported by the CVE source.
- Oct 27, 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 <=<= 3.0.1
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