dbcve.org
Image Map ProWordPress extension · Webcraftplugins

CVE-2023-3412

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-27
Fix available
A fix is available. Upgrade to after 1.0.0 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 Image Map Pro – Drag-and-drop Builder for Interactive Images – Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.0.0. This is due to a missing capability check on the ajax_store_save() function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to modify plugin settings and inject malicious web scripts.

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 Lite WordPress plugin versions up to 1.0.0 are vulnerable to stored Cross-Site Scripting due to missing capability checks on the ajax_store_save() function. This allows authenticated users with minimal subscriber-level permissions to modify plugin settings and inject malicious JavaScript that executes when settings are accessed.

MitigationApply any available vendor patch; if no patch exists, add a capability check (e.g., current_user_can('manage_options')) to the ajax_store_save() function and sanitize all settings input before storage.

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:<= 1.0.0

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. Confirm plugin installation and version
    Locate the plugin in the WordPress plugins directory (wp-content/plugins/) and check the main plugin file header or readme.txt for the version number
    Affected if The installed version is 1.0.0 or any version up to 1.0.0 inclusive
  2. Identify the vulnerable ajax_store_save function
    Search the plugin files for the ajax_store_save() function definition, typically in the main plugin PHP file or an includes/ajax.php file
    Affected if The ajax_store_save function exists in the plugin code
  3. Check for capability restrictions on ajax_store_save
    Examine the ajax_store_save function code to see if it includes a capability check such as current_user_can() before processing requests
    Affected if The function lacks a capability check (e.g., current_user_can('manage_options')) and can be accessed by low-privilege users
  4. Verify subscriber-level access is exploitable
    Test whether an authenticated user with the Subscriber role can access and trigger the ajax_store_save function via admin-ajax.php or similar endpoint
    Affected if Subscriber-level users can successfully trigger the ajax_store_save function without authorization
  5. Inspect plugin settings for injected scripts
    Access the plugin settings page in WordPress admin and examine stored configuration values, or query the WordPress options table for Image Map Pro settings containing script tags or javascript: protocols
    Affected if Plugin settings contain unsanitized JavaScript code or suspicious script tags

You are affected if Image Map Pro Lite version 1.0.0 or below is installed and the ajax_store_save function lacks capability checks, allowing subscriber-level users to inject and store malicious scripts.

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

Apply any available vendor patch; if no patch exists, add a capability check (e.g., current_user_can('manage_options')) to the ajax_store_save() function and sanitize all settings input before storage.

Recommended fix Moderate confidence

Latest version of Image Map Pro Lite on WordPress.org (version higher than 1.0.0)

  1. Check the WordPress admin dashboard for plugin updates under Plugins > All Plugins
  2. Update Image Map Pro Lite to the latest available version from the official WordPress plugin repository
  3. Verify the update was successful and test that the plugin functionality works as expected
  4. Confirm that the ajax_store_save() function now includes proper capability checks (contributor level or higher)

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

Fix this in Image Map Pro Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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