Mapster Wp MapsWordPress extension · Mapster
CVE-2024-21744
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 Mapster Technology Inc. Mapster WP Maps allows Stored XSS.This issue affects Mapster WP Maps: from n/a through 1.2.38.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in Mapster WP Maps plugin allows authenticated attackers to inject malicious JavaScript code through map configuration inputs. The injected payload executes when administrators or other users view map data in the WordPress admin dashboard or on the frontend.
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
Mapster Wp MapsWordPress extension
<= 1.2.38CVSS 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.
-
Verify Mapster WP Maps plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Mapster WP Maps' or 'Mapster Maps' in the plugin list.Affected if plugin is not installed in the WordPress environment
-
Check installed plugin versionIn the plugins list, locate the Mapster WP Maps entry and note the version number displayed. Compare this version against the affected range: version 1.2.38 or earlier.Affected if installed version is 1.2.38 or lower
-
Confirm map configurations existNavigate to the Mapster Maps settings or maps list in the WordPress admin dashboard (usually under Maps or a dedicated Mapster menu item). Check if any map configurations have been created.Affected if at least one map configuration has been created and saved
-
Identify user access to map editingReview WordPress user roles that have access to create or edit map configurations. This is typically found under Mapster plugin settings or WordPress user role capabilities.Affected if any user role other than Administrator has permission to create or edit maps
Environment is affected if Mapster WP Maps plugin version 1.2.38 or lower is installed AND map configurations have been created, because the stored XSS vulnerability exists in map configuration inputs that can be authored by authenticated users.
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 dataUpgrade Mapster WP Maps to version 1.2.39 or later which includes proper input sanitization and output encoding for all map-related user inputs.
Fix this in Mapster Wp Maps
Scoped from the published advisory
- 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-2024-21744 — 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-21744 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