dbcve.org
OpenstreetmapWordPress extension · Hyumika

CVE-2022-30544

HIGH · 8.8 CVSS v3.1 Published 2023-01-17
Fix available
A fix is available. Upgrade to after 6.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) in MiKa's OSM – OpenStreetMap plugin <= 6.0.1 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

Cross-Site Request Forgery (CSRF) vulnerability in MiKa's OSM WordPress plugin allows remote attackers to trick authenticated administrators into performing unwanted actions by leveraging the lack of anti-CSRF token validation on state-changing operations.

MitigationImplement WordPress nonces (nonce_tokens) on all form submissions and AJAX requests that perform state-changing operations, and verify the nonce before processing any administrative action.

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.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Hyumika Openstreetmap plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Hyumika Openstreetmap' or 'MiKa's OSM' in the list. Note whether it is activated.
    Affected if The plugin is present and activated in WordPress
  2. Confirm installed version number
    On the Plugins page, click on the plugin name or view details to display the version number. Compare it to the affected range: <= 6.0.1
    Affected if Version number is 6.0.1 or lower
  3. Inspect plugin for missing nonce validation
    Access the plugin files via wp-content/plugins/hyumika-openstreetmap or similar path. Search PHP files for state-changing admin actions (settings save, map configuration updates, data import). Look for wp_verify_nonce, check_admin_referer, or nonce verification calls around form handlers and AJAX endpoints.
    Affected if State-changing operations (form submissions, AJAX requests) lack nonce verification before processing
  4. Identify unprotected form actions
    Examine plugin PHP files for HTML forms that perform admin actions. Check if these forms include wp_nonce_field or similar nonce tokens in their output. Look for forms missing the 'nonce' or '_wpnonce' hidden fields.
    Affected if Admin forms lack nonce token hidden fields
  5. Check AJAX handlers for nonce verification
    Search plugin files for add_action calls registering AJAX endpoints (wp_ajax_). Locate the callback functions and verify they call wp_verify_nonce or check_admin_referer before executing state-changing logic.
    Affected if AJAX handlers processing state-changing requests do not validate nonces

If the Hyumika Openstreetmap plugin version is 6.0.1 or lower and state-changing operations (forms or AJAX endpoints) lack nonce verification, the environment is vulnerable to CVE-2022-30544.

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.1
Interim mitigation

Implement WordPress nonces (nonce_tokens) on all form submissions and AJAX requests that perform state-changing operations, and verify the nonce before processing any administrative action.

Recommended fix Moderate confidence

latest version available in the WordPress.org plugin repository (version 6.0.2 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'MiKa's OSM – OpenStreetMap' in the plugin list
  4. Check the current installed version is 6.0.1 or below
  5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress.org plugin repository
  6. After updating, verify the new version number in the plugins list to confirm the update was successful

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

Fix this in Openstreetmap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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