CVE-2025-24504
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn improper input validation the CSRF filter results in unsanitized user input written to the application logs.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe CSRF filter component improperly validates input, allowing unsanitized user-controlled data to be written directly to application logs. This could enable log injection attacks where malicious content is embedded in log files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if a CSRF filter component is in useSearch application configuration files, dependencies, or source code for CSRF filter implementations (e.g., references to CSRF, cross-site request forgery, filter, or token validation). Review deployed libraries and frameworks for CSRF-related modules.Affected if A CSRF filter component is present and active in the environment
-
Determine if logging is enabled for CSRF-related operationsReview application logging configuration to check if CSRF filter events, token validation results, or request metadata are being written to log files. Look for log statements capturing CSRF tokens, request headers, or form parameters.Affected if CSRF filter activity or input data is being logged
-
Check if user-controlled input reaches logs unsanitizedExamine the CSRF filter code or configuration to verify whether user-supplied data (such as tokens, referer headers, or request parameters) is written to logs without encoding, validation, or sanitization. Inspect actual log output for raw user input.Affected if User-controlled data from CSRF operations is written directly to logs without sanitization
-
Compare the deployed CSRF filter version to any available patchIf a vendor or open-source project maintains the CSRF filter, identify the installed version from dependency manifests, library files, or version headers. Compare against any fixed versions noted in security advisories.Affected if The installed version is unpatched or predates available fixes
The environment is affected if a CSRF filter is enabled and writes user-supplied input directly to logs without sanitization, enabling log injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input sanitization on user data before it is written to logs, and consider validating/encoding CSRF token input at the filter level.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24504 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data