Browser script execution via crafted 400 response
Published Oct 24, 2024 · Updated Oct 24, 2024
Cross-site scripting in baserCMS 5.1.1 and earlier allows remote attackers to execute script in a victim's browser through a 400 response. The project advisory identifies the HTTP 400 response as the execution locus but does not disclose which request field is rendered or how output encoding fails. No account is required, but a victim must load the crafted response; script then runs in the site's browser origin and can read or alter accessible page data.
Summary
What happened
Cross-site scripting in baserCMS 5.1.1 and earlier allows remote attackers to execute script in a victim's browser through a 400 response. The project advisory identifies the HTTP 400 response as the execution locus but does not disclose which request field is rendered or how output encoding fails. No account is required, but a victim must load the crafted response; script then runs in the site's browser origin and can read or alter accessible page data.
The record
- CVE
- CVE-2024-46995
- Published
- Oct 24, 2024
- Updated
- Oct 24, 2024
- Vendor
- baserCMS Users Community
- Product
- baserCMS
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 24, 2024CVE publishedPublication date reported by the CVE source.
- Oct 24, 2024Record 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=< 5.1.2
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