dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-32113

HIGH · 7.1 CVSS v3.1 Published 2025-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Renzo Tejada Libro de Reclamaciones y Quejas libro-de-reclamaciones-y-quejas allows Cross Site Request Forgery.This issue affects Libro de Reclamaciones y Quejas: from n/a through <= 1.0.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the 'Libro de Reclamaciones y Quejas' application (version <= 1.0) allows remote attackers to trick authenticated users into performing unintended actions such as submitting false complaints or modifying claim data. The application lacks proper anti-CSRF token validation or origin checking, enabling attackers to craft malicious requests that the server accepts as legitimate.

MitigationImplement anti-CSRF tokens for all state-changing operations (forms) and validate Origin/Referer headers server-side. Additionally, configure SameSite attributes on session cookies to 'Lax' or 'Strict'.

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of the application
    Locate the application version number in the software itself, configuration files, or the 'about' section of the 'Libro de Reclamaciones y Quejas' application. Compare it against version 1.0.
    Affected if The installed version is 1.0 or any version lower than 1.0.
  2. Inspect HTML forms for anti-CSRF tokens
    View the page source of complaint submission forms or any form that modifies claim data. Look for a hidden input field containing a token value (often named 'csrf_token', 'token', or similar) or check if forms submit tokens via headers.
    Affected if No anti-CSRF token is present in the HTML forms, or tokens are missing entirely.
  3. Verify server-side Origin or Referer header validation
    Submit a request to the application from an unauthorized origin (or modify the Origin header in a request) and observe whether the server rejects it. Alternatively, review server-side code or proxy logs to see if Origin/Referer headers are checked before processing state-changing requests.
    Affected if The server accepts requests with mismatched or missing Origin/Referer headers without rejecting them.
  4. Examine session cookie SameSite attribute
    Use browser developer tools or a command-line HTTP client to inspect the session cookie set by the application. Check if the Set-Cookie header includes the SameSite attribute with a value of 'Lax' or 'Strict'.
    Affected if The session cookie has no SameSite attribute, or SameSite is set to 'None' without secure flag.
  5. Test for CSRF vulnerability via proof-of-concept request
    Craft a minimal HTML page with a form that submits to the application's complaint submission endpoint without a valid token. Host this page and attempt to have an authenticated user trigger the form. Observe if the action succeeds.
    Affected if The malicious request succeeds and the server processes it without requiring a valid anti-CSRF token or valid Origin header.

A user is affected if the application version is 1.0 or lower AND any of the following are true: no anti-CSRF tokens exist in forms, server does not validate Origin/Referer headers, or session cookies lack SameSite attribute.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens for all state-changing operations (forms) and validate Origin/Referer headers server-side. Additionally, configure SameSite attributes on session cookies to 'Lax' or 'Strict'.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32113 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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