dbcve.org
Image Map ProWordPress extension · Webcraftplugins

CVE-2024-9584

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-25
Fix available
A fix is available. Upgrade to after 6.0.20 or later.
See remediation →
60/100
Remediation priority · Elevated
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 Image Map Pro plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the AJAX functions in versions up to, and including, 6.0.20. This makes it possible for authenticated attackers with contributor-level privileges or above, to add, update or delete map projects.

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 Image Map Pro WordPress plugin has a broken access control vulnerability where AJAX functions lack proper capability checks. This allows any authenticated user with contributor-level privileges or higher to add, update, or delete map projects via AJAX calls, leading to unauthorized data modification or loss.

MitigationApply any available vendor patch for Image Map Pro. If no patch exists, implement proper WordPress capability checks (e.g., current_user_can()) on all affected AJAX handlers to verify user permissions before allowing map project operations.

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
Image Map ProWordPress extension
Affected:<= 6.0.20

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
None
Integrity
Low
Availability
Low

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

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 Image Map Pro plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Image Map Pro' by Webcraftplugins. Note the installed version number displayed.
    Affected if The plugin is installed and the version shown is 6.0.20 or lower
  2. Check WordPress user account privilege levels
    Navigate to Users in WordPress admin panel. Review the roles assigned to users (Administrator, Editor, Author, Contributor, Subscriber). Identify any users with Contributor-level access or higher.
    Affected if There are user accounts with Contributor, Author, Editor, or Administrator roles who have access to the WordPress admin
  3. Inspect AJAX handler registration for capability checks
    Locate the plugin PHP files (typically in wp-content/plugins/image-map-pro-wordpress/). Search for 'add_action' calls registering AJAX handlers (keywords: 'wp_ajax_imagemappro', 'wp_ajax_nopriv'). Examine whether 'current_user_can()' or similar capability checks appear before any map project operations.
    Affected if AJAX handlers exist without capability verification or only check for any logged-in user without role restrictions
  4. Verify AJAX endpoints are accessible to lower-privileged users
    Using browser dev tools or a tool like Burp Suite, capture a WordPress request while logged in as a Contributor user. Submit an AJAX request to typical Image Map Pro endpoints (often /wp-admin/admin-ajax.php with action parameter like 'imagemappro_save' or similar). Confirm the request completes without 403/401 errors.
    Affected if AJAX requests to map project operations (add/update/delete) succeed when made by a Contributor-level user without receiving permission denied errors

Your environment is affected if Image Map Pro plugin version 6.0.20 or lower is installed and you have users with Contributor-level access or higher, especially if AJAX handlers lack role-based capability verification.

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

Apply any available vendor patch for Image Map Pro. If no patch exists, implement proper WordPress capability checks (e.g., current_user_can()) on all affected AJAX handlers to verify user permissions before allowing map project operations.

Fix this in Image Map Pro 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-2024-9584 — 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-9584 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