CVE-2025-30588
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 ryan_xantoo Map Contact map-contact allows Stored XSS.This issue affects Map Contact: from n/a through <= 3.0.4.
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 · high confidenceCSRF vulnerability in the WordPress plugin 'Map Contact' (map-contact) allows unauthenticated or authenticated attackers to inject malicious JavaScript code through forged form submissions, resulting in Stored XSS. This affects versions up to and including 3.0.4.
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 Map Contact plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Map Contact' (map-contact). Note the displayed version number.Affected if Plugin is installed and version is 3.0.4 or lower
-
Confirm installed version against affected rangeCompare the installed version number to '3.0.4'. Check the plugin's main file header or the plugins page for the exact version string.Affected if Version is 3.0.4 or any version up to and including 3.0.4
-
Locate the plugin form handling codeAccess the WordPress file system via FTP or file manager. Navigate to wp-content/plugins/map-contact/ and examine PHP files that handle form submissions (commonly functions.php, map-contact.php, or files containing 'submit', 'post', 'form' in the name).Affected if Plugin files exist and handle form submissions without verifying CSRF tokens
-
Inspect for missing CSRF protection in form handlersSearch the plugin PHP files for 'wp_nonce_field', 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer'. Look at functions that process form data from $_POST or $_REQUEST.Affected if Form processing code lacks nonce verification functions, allowing forged submissions
-
Check for stored malicious submissions in the databaseAccess the WordPress database via phpMyAdmin or command line. Query tables that store plugin data (often wp_options or custom tables with 'map_contact' or 'contact' in the name) for suspicious script tags, iframe elements, or encoded JavaScript patterns.Affected if Database contains entries with script tags, event handlers (onload, onclick), or encoded payloads that could indicate exploited XSS
User is affected if the Map Contact plugin is installed at version 3.0.4 or below and form submissions are processed without CSRF token validation.
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 dataAdd anti-CSRF nonces to all form submissions and implement proper input sanitization with output encoding to prevent stored XSS attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30588 — 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-30588 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