CVE-2025-26768
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 what3words what3words Address Field 3-word-address-validation-field allows Stored XSS.This issue affects what3words Address Field: from n/a through <= 4.0.15.
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 the what3words Address Field plugin (versions <= 4.0.15) allows authenticated users to be tricked into submitting malicious requests that inject stored XSS payloads into the plugin's settings or address validation fields, which are then rendered without proper sanitization.
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.
-
Identify if what3words Address Field plugin is installedCheck your WordPress plugins directory for a folder named 'what3words-address-field' or 'w3w-address-field', or query the wp_options table for active plugins containing 'what3words'Affected if The plugin folder or database entry exists and the plugin is present in your environment
-
Check the installed plugin versionLocate the main plugin PHP file (typically what3words-address-field.php) and look for the version comment header, or query the WordPress plugins API for the installed versionAffected if The version number is 4.0.15 or lower
-
Verify if the plugin is activeCheck the wp_options table for the active_plugins option, or view the Plugins page in WordPress admin dashboardAffected if The plugin shows as active in the WordPress admin or active_plugins option contains the what3words plugin entry
-
Inspect plugin settings for XSS payloadsQuery the wp_options table for options containing 'what3words' (e.g., w3w_settings, what3words_options) and examine stored values for script tags, event handlers, or encoded XSS patternsAffected if Any stored option values contain unsanitized HTML, script tags, or XSS vectors like <script>, onerror=, javascript:, or encoded variants
-
Check for missing CSRF protection in form submissionsReview the plugin's PHP files for form handlers and state-changing operations; search for presence of wp_nonce_field, wp_verify_nonce, or check_admin_referer calls in settings update and address submission functionsAffected if Form processing code lacks nonce verification or uses nonces incorrectly (e.g., nonce check after the action executes)
You are affected if the what3words Address Field plugin is installed at version 4.0.15 or lower and is active in your WordPress environment, particularly if settings contain unsanitized data or the plugin lacks CSRF nonce protection in its form handlers.
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 (nonces) on all form submissions and state-changing operations, and ensure all user-supplied input is properly sanitized before storage and escaped before output.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26768 — 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-26768 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