dbcve.org
Cbx MapWordPress extension · Codeboxr

CVE-2024-22297

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-31
Fix available
A fix is available. Upgrade to after 1.1.11 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Codeboxr CBX Map for Google Map & OpenStreetMap allows Stored XSS.This issue affects CBX Map for Google Map & OpenStreetMap: from n/a through 1.1.11.

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 confidence

Stored XSS vulnerability in Codeboxr CBX Map plugin allows attackers to inject malicious JavaScript through unsanitized user input (likely map marker or location fields) that gets stored and executed when other users view the affected map pages.

MitigationUpdate the CBX Map plugin to the latest version (beyond 1.1.11) which should contain proper input sanitization; alternatively, disable the plugin until a patch is available.

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
Cbx MapWordPress extension
Affected:<= 1.1.11

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Codeboxr CBX Map plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Codeboxr CBX Map' or 'CBX Map' in the list. Note the version number displayed alongside the plugin name.
    Affected if The plugin appears in the installed plugins list with a version number at or below 1.1.11
  2. Compare installed version to affected range
    If the plugin is installed, compare the displayed version number against the affected range: any version <= 1.1.11 is vulnerable. The latest version beyond 1.1.11 contains the fix.
    Affected if Installed version is 1.1.11 or lower
  3. Identify maps with custom markers or locations
    Navigate to the plugin settings or map configuration pages in the WordPress admin. Look for any maps that have custom markers, location names, coordinates, or address fields that were manually entered or could contain user-supplied data.
    Affected if Maps exist that contain manually configured marker names, location titles, or address fields that accept freeform text input
  4. Inspect stored marker/location data for unsanitized content
    Access the WordPress database via phpMyAdmin or wp-cli. Query the posts table or any custom plugin tables (commonly prefixed with cbxmap or similar) for entries containing map marker or location data. Look for HTML tags, script tags, or javascript: URIs in fields that should only contain plain text.
    Affected if Database entries in marker or location fields contain raw HTML, script tags, or javascript: protocols that were not escaped or sanitized upon storage

The environment is affected if the Codeboxr CBX Map plugin is installed with version 1.1.11 or lower AND maps with manually entered markers or locations exist in the system, particularly if those fields contain unsanitized HTML or script content in the database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.1.11
Interim mitigation

Update the CBX Map plugin to the latest version (beyond 1.1.11) which should contain proper input sanitization; alternatively, disable the plugin until a patch is available.

Fix this in Cbx Map Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22297 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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