dbcve.org
OpenstreetmapWordPress extension · Hyumika

CVE-2024-3604

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to after 6.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 SQL Injection via the 'tagged_filter' attribute of the 'osm_map_v3' shortcode in all versions up to, and including, 6.0.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 plugin for WordPress is vulnerable to SQL Injection in the 'osm_map_v3' shortcode's 'tagged_filter' parameter. Authenticated attackers with contributor-level access can inject malicious SQL queries due to insufficient input escaping and lack of prepared statement usage, allowing extraction of sensitive database information.

MitigationUpdate the OSM – OpenStreetMap plugin to version 6.0.4 or later which patches the SQL injection vulnerability by implementing proper input sanitization and using prepared SQL statements.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 the OSM plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'OSM - OpenStreetMap' or 'Hyumika Openstreetmap' plugin. Note the installed version number displayed there.
    Affected if The plugin is installed and the version is 6.0.2 or lower.
  2. Confirm the exact plugin version
    Click on the plugin name in the WordPress plugins list to view the version details, or check the plugin header in /wp-content/plugins/osm/ directory if you have file access.
    Affected if The version displayed is 6.0.2 or lower, indicating the vulnerable version is installed.
  3. Search for usage of the vulnerable shortcode with tagged_filter
    Search your WordPress database or content files (posts, pages, widgets) for the string 'osm_map_v3' combined with 'tagged_filter'. Use WP CLI: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%osm_map_v3%' AND post_content LIKE '%tagged_filter%'" or search theme files for the shortcode registration.
    Affected if The shortcode 'osm_map_v3' with the 'tagged_filter' parameter is actively used in any post, page, or widget content.
  4. Review user role permissions
    In WordPress admin, go to Users > All Users and check if any users exist with Contributor, Author, Editor, or Administrator roles. The vulnerability is exploitable by any authenticated user with Contributor-level access or higher.
    Affected if There are user accounts with Contributor-level access or higher, particularly untrusted or external users.

Your environment is affected if the OSM - OpenStreetMap plugin version is 6.0.2 or lower AND the osm_map_v3 shortcode with tagged_filter parameter is in use AND you have users with at least Contributor-level access.

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 which patches the SQL injection vulnerability by implementing proper input sanitization and using prepared SQL statements.

Recommended fix High confidence

Upgrade to OSM – OpenStreetMap version 6.0.4

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'OSM – OpenStreetMap' plugin
  4. Click 'Update now' if an update is available, or manually download version 6.0.4 from wordpress.org and upload via Plugins > Add New > Upload Plugin
  5. Verify the update completed successfully

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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