dbcve.org
OpenstreetmapWordPress extension · Hyumika

CVE-2024-3603

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to after 6.0.2 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
The OSM – OpenStreetMap plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'osm_map' shortcode in all versions up to, and including, 6.0.3 due to insufficient input sanitization and output escaping on user supplied attributes such as 'theme'. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The OSM – OpenStreetMap WordPress plugin (versions up to 6.0.3) contains a stored XSS vulnerability in the osm_map shortcode. The 'theme' attribute parameter is not sanitized on input or escaped on output, allowing authenticated users with contributor-level access or higher to inject arbitrary JavaScript that executes when other users view the affected page.

MitigationUpdate the OSM – OpenStreetMap plugin to version 6.0.4 or later. Until patched, review user permissions and consider restricting shortcode usage to trusted roles only.

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
OpenstreetmapWordPress extension
Affected:<= 6.0.2

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 OSM - OpenStreetMap plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'OSM - OpenStreetMap' or check the plugins directory for the osm-openstreetmap folder
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find OSM - OpenStreetMap, and note the version number displayed
    Affected if The version is 6.0.2 or below (6.0.3 is also affected as the fix was in 6.0.4)
  3. Search for osm_map shortcode usage
    Use WordPress search or a database query to find posts/pages containing '[osm_map' shortcode, or check theme/template files for osm_map shortcode calls
    Affected if The osm_map shortcode is present in any published content
  4. Review user roles with shortcode access
    In WordPress admin, go to Users and examine which roles exist; contributor role or higher allows shortcode creation
    Affected if There are users with contributor, author, editor, or administrator roles who could inject the malicious theme attribute

The environment is affected if the OSM - OpenStreetMap plugin versions 6.0.2 or below are installed AND the osm_map shortcode is in use, regardless of user role configuration.

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 6.0.2
Interim mitigation

Update the OSM – OpenStreetMap plugin to version 6.0.4 or later. Until patched, review user permissions and consider restricting shortcode usage to trusted roles only.

Recommended fix Moderate confidence

Upgrade to OSM – OpenStreetMap plugin version 6.0.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'OSM – OpenStreetMap' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 6.0.3 or later
  5. 5. Alternatively, download version 6.0.3 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 6.0.3 or higher

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

Fix this in Openstreetmap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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