dbcve.org
Cbx MapWordPress extension · Codeboxr

CVE-2023-47240

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-16
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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Codeboxr CBX Map for Google Map & OpenStreetMap plugin <= 1.1.11 versions.

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 confidence

Authenticated users with contributor+ privileges can inject malicious JavaScript code through the plugin's map configuration settings. The payload is stored in the database and executes when other users view the map, allowing session hijacking, defacement, or redirecting authenticated users to malicious sites.

MitigationUpdate the Codeboxr CBX Map plugin to version 1.1.12 or later which includes proper input sanitization. Alternatively, implement output encoding and input validation on all user-supplied data before rendering.

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 of active plugins.
    Affected if The plugin appears in the list and is activated.
  2. Check installed plugin version
    In the plugins list, click on the plugin name or view details to display the installed version number. Compare this version against the affected range: <= 1.1.11.
    Affected if The installed version is 1.1.11 or earlier.
  3. Inspect map configuration settings in database
    Access the WordPress database via phpMyAdmin or CLI. Query the options table for map-related settings: SELECT * FROM wp_options WHERE option_name LIKE '%cbxmap%' or similar. Examine the option_value fields for suspicious content.
    Affected if The database contains unescaped HTML script tags, javascript: URIs, or event handler attributes (onload, onerror, onclick) in map configuration values.
  4. Identify users with contributor+ privileges
    Navigate to Users > All Users in WordPress admin. Review the role column for users assigned 'Contributor', 'Author', 'Editor', or 'Administrator' roles who have access to create or edit maps.
    Affected if Any user with contributor-level access or higher exists on the site.
  5. Review map post meta for stored XSS
    Query the postmeta table for entries associated with map custom post types: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%cbxmap%' or WHERE meta_value LIKE '%<script%'. Inspect stored values for encoded or plain JavaScript payloads.
    Affected if Map post meta entries contain script tags, iframe embeddings, or other potentially malicious script content.

A user is affected if the Codeboxr CBX Map plugin version is 1.1.11 or earlier AND contributor-level users exist on the site AND the database contains unescaped HTML/JavaScript in map configuration or post meta tables.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.1.11
Interim mitigation

Update the Codeboxr CBX Map plugin to version 1.1.12 or later which includes proper input sanitization. Alternatively, implement output encoding and input validation on all user-supplied data before rendering.

Recommended fix Moderate confidence

Latest version after 1.1.11 (check WordPress plugin repository for current release)

  1. 1. Check the official WordPress plugin repository or Codeboxr website for the latest version of the CBX Map plugin
  2. 2. Update the Codeboxr CBX Map plugin to the latest available version (after version 1.1.11)
  3. 3. Verify the update was successful by checking the installed version number
  4. 4. Test the map functionality to ensure the plugin still works correctly after the update
  5. 5. Clear any caching plugins if the changes are not immediately reflected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cbx Map Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47240 — 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-2023-47240 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