Persistent XSS via insufficient file replacement validation
Published Jan 9, 2025 · Updated Jan 9, 2025
Persistent XSS in Drupal File Entity before 7.x-2.38 allows remote authenticated users to inject script through file replacement. The replacement workflow insufficiently validates the replacement file, allowing attacker-controlled content to persist and execute when another user views it. A role with permission to edit files is required, and execution also requires another user to view the stored content.
Summary
What happened
Persistent XSS in Drupal File Entity before 7.x-2.38 allows remote authenticated users to inject script through file replacement. The replacement workflow insufficiently validates the replacement file, allowing attacker-controlled content to persist and execute when another user views it. A role with permission to edit files is required, and execution also requires another user to view the stored content.
The record
- CVE
- CVE-2024-13237
- Published
- Jan 9, 2025
- Updated
- Jan 9, 2025
- Vendor
- OAuth.js
- Product
- File Entity (fieldable files)
- Classifications
- CWE-79, CAPEC-63, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2025CVE publishedPublication date reported by the CVE source.
- Jan 9, 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=7.x-* <7.x-2.38
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