CVE-2024-38457 Xenforo before 2.2.16 allows CSRF.
High 8.8
Published
Updated
Check this codebase for CVE-2024-38457 and fix it if it is affected.
What it is: CVE-2024-38457 is a high-severity vulnerability in n/a, published on 16 Jun 2024.
Exploitation: There is no known exploitation of CVE-2024-38457 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2024-38457/ (Markdown: https://insights.sbomify.com/CVE-2024-38457/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2024-38457?
CVE-2024-38457 is a high-severity vulnerability in n/a, published on 16 Jun 2024.
Official description
Xenforo before 2.2.16 allows CSRF.
Weakness: CWE-352
Which versions are affected by CVE-2024-38457?
It affects 1 product.
Products include Xenforo Xenforo.
How do I fix CVE-2024-38457?
No fix has been published for CVE-2024-38457 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-38457 being exploited?
There is no known exploitation of CVE-2024-38457 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2025-71279 XenForo Passkey Security Bypass
- CVE-2026-73309 XenForo < 2.3.13 Authentication Bypass via OAuth2 Token Endpoint
- CVE-2026-73311 XenForo < 2.3.13 OAuth2 Authorization Code Reuse
- CVE-2026-73312 XenForo < 2.3.13 Refresh Token Replay via Expired Access Token
- CVE-2024-38458 Code injection in n/a
Sources
Also known as GHSA-h362-fq3p-pqgm.