🛡️ CVE-2024-53829 — codechecker
Description
Cross-Site Request Forgery in CodeChecker API
Summary
Cross-site request forgery allows an unauthenticated attacker to hijack the authentication of a logged in user, and use the web API with the same permissions.
Details
Security attributes like HttpOnly and SameSite are missing from the session cookie, allowing its use from XHR requests and form submissions.
The CodeChecker API endpoints only require the session cookie, they do not require a CSRF token, and missing HTTP headers allow the form submission to succeed (but not XHR). This means that the attacker needs to know the ID of products to edit or delete them, but it does not need knowledge to create new products with the SQLite backend.
PoC
With a superuser logged into CodeChecker.
```html
<html><body>
<form action="https://codechecker.example.com/v6.58/Products" method="POST" enctype="text/plain">
<input type="text" name='[1,"getProducts",1,1,{}]' value=''>
</form>
<script>document.forms[0].submit()</script>
</body></html>
```
Or the same form attack on any of the applicable endpoints.
Impact
The vulnerability allows an attacker to make requests to CodeChecker as the currently logged in user, including but not limited to adding, removing or editing products. The attacker needs to know the ID of the available products to modify or delete them. The attacker cannot directly exfiltrate data from CodeChecker, due to being limited to form-based CSRF.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity high, availability none.
Weakness class
CVE-2024-53829 is classified as CWE-352: Cross-Site Request Forgery (CSRF). A state-changing request is accepted without proof it was intended, so another site can trigger it using the victim's session.
Affected software
CVE-2024-53829 is recorded against 1 package.
- codechecker (fixed in 6.24.5)
Timeline and source
Published on 21 January 2025 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. Record sourced from OSV.
References
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Package)
github.com (Web)
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| codechecker | — | 6.24.5 |
References
Similar Threats
- Critical CVE-2026-25660
- Medium CVE-2025-40843
- Medium CVE-2025-1300
- Critical CVE-2024-10081
- Critical CVE-2024-10082
More CVE 2024 advisories
Browse all of CVE 2024 in the advisory index.
Exploit Protection
Are you running codechecker?
CVE-2024-53829 carries CVSS 8.0 High rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.
Check My Site For CVE-2024-53829 →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.