Anonymous page disruption via XHR cache poisoning
Published Feb 4, 2025 · Updated Feb 4, 2025
Cache poisoning in Discourse stable before 3.3.2 and tests-passed before 3.4.0.beta3 allows remote attackers to disrupt anonymous page responses. The anonymous response cache accepts a response produced by an attacker-crafted XHR request as a reusable entry, so later cache hits can omit preloaded data. The attack requires anonymous caching to be enabled, and its reported effects are limited to anonymous visitors.
Summary
What happened
Cache poisoning in Discourse stable before 3.3.2 and tests-passed before 3.4.0.beta3 allows remote attackers to disrupt anonymous page responses. The anonymous response cache accepts a response produced by an attacker-crafted XHR request as a reusable entry, so later cache hits can omit preloaded data. The attack requires anonymous caching to be enabled, and its reported effects are limited to anonymous visitors.
The record
- CVE
- CVE-2024-55948
- Published
- Feb 4, 2025
- Updated
- Feb 4, 2025
- Vendor
- Discourse
- Product
- Discourse
- Classifications
- CWE-346
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 4, 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=stable: < 3.3.2
- Affected versionversion=tests-passed: < 3.4.0.beta3
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