Geo MashupWordPress extension · Cyberhobo
CVE-2024-44008
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Dylan Kuhn Geo Mashup geo-mashup allows Stored XSS.This issue affects Geo Mashup: from n/a through <= 1.13.12.
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 Geo Mashup WordPress plugin up to version 1.13.12 contains a stored cross-site scripting (XSS) vulnerability due to improper neutralization of user input during web page generation. Attackers can inject malicious scripts that execute in the browsers of users viewing the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Geo MashupWordPress extension
< 1.13.13CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Locate the Geo Mashup plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Geo Mashup' in the list. The version number is displayed below the plugin name. Alternatively, check the main plugin file (geo-mashup.php) in wp-content/plugins/geo-mashup/ and look for the 'Version' header in the file comments.Affected if The displayed version is less than 1.13.13 (for example, 1.13.12, 1.13.10, etc.)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins. Confirm that Geo Mashup shows 'Active' status under the plugin name.Affected if The plugin is active and the version is below 1.13.13.
-
Check for user-generated content locationsReview pages or posts where the Geo Mashup shortcode or widget is used, particularly any custom location data or map marker content that may accept user input.Affected if The plugin displays user-supplied location names, descriptions, or custom data fields without visible evidence of encoding.
You are affected if Geo Mashup version 1.13.12 or lower is installed and active on your WordPress site.
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.
dbcve · scoped1.13.13
Update Geo Mashup to the latest patched version. If no update is available, implement output encoding and input validation on all user-supplied data before rendering in the browser.
Geo Mashup 1.13.13
- Backup your WordPress site database and files before performing any updates
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Find Geo Mashup in the plugin list
- Click 'Update now' on Geo Mashup to update to version 1.13.13
- Alternatively, go to Plugins > Add New > Upload and upload version 1.13.13 of Geo Mashup
- Verify the plugin version shows 1.13.13 after update
- Test that the plugin functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Geo Mashup
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-44008 — 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-2024-44008 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