CVE-2025-23664
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Real Seguro Viagem Real Seguro Viagem seguro-viagem allows Stored XSS.This issue affects Real Seguro Viagem: from n/a through <= 2.0.5.
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 confidenceCSRF vulnerability in Real Seguro Viagem (seguro-viagem) plugin allows attackers to inject malicious scripts via Stored XSS by tricking authenticated users into submitting crafted requests. The lack of proper CSRF token validation on form submissions enables cross-site request forgery that results in persistent script execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify seguro-viagem plugin is installedCheck for the plugin directory at wp-content/plugins/seguro-viagem/ or search for 'Real Seguro Viagem' in WordPress admin under PluginsAffected if Plugin is present in the WordPress installation
-
Identify installed plugin versionOpen the main plugin PHP file (usually seguro-viagem.php) and locate the version comment or Version header in the plugin file headerAffected if Version cannot be determined or is unknown, treat as potentially affected
-
Inspect form submissions for CSRF tokensExamine PHP files handling form submissions (look for $_POST or $_GET processing) and check if they use wp_verify_nonce() or check_admin_referer() functionsAffected if Form handlers lack nonce verification functions, indicating CSRF protection is missing
-
Verify nonce validation on state-changing actionsSearch plugin PHP files for 'admin_post', 'wp_ajax', or form action handlers and confirm they validate nonces before processing dataAffected if State-changing actions (save, update, delete) do not validate CSRF tokens
-
Check if stored data is output-encodedSearch for echo or print statements outputting plugin-generated data and verify if they use esc_html(), esc_attr(), or similar escaping functionsAffected if User-supplied data is output without encoding, increasing XSS risk if CSRF is exploited
If the seguro-viagem plugin is installed and form submissions lack CSRF token validation (nonce checks), the environment is affected by this vulnerability.
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 anti-CSRF tokens (synchronizer token pattern) on all state-changing forms and validate origin/target headers. Additionally, apply output encoding on user-supplied data to mitigate XSS even if CSRF controls are bypassed.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23664 — 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-23664 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