dbcve.org
Interactive Svg Image Map BuilderWordPress extension · Wpmart

CVE-2022-45846

HIGH · 8.8 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 5.6.9 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) vulnerability in Nickys Image Map Pro for WordPress - Interactive SVG Image Map Builder plugin < 5.6.9 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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Image Map Pro WordPress plugin allows attackers to induce authenticated administrators to perform unintended actions (such as modifying image map settings or configurations) by tricking them into visiting malicious URLs. The lack of proper nonce verification on sensitive admin actions enables the forgery attack.

MitigationUpdate Image Map Pro plugin to version 5.6.9 or later, which should include proper nonce verification for admin actions to prevent CSRF attacks. Until updated, avoid clicking untrusted links while logged into WordPress admin.

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
Interactive Svg Image Map BuilderWordPress extension
Affected:< 5.6.9

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 Image Map Pro plugin is installed
    Log into WordPress admin and go to Plugins > Installed Plugins, or use WP-CLI: wp plugin list --name='image-map-pro'
    Affected if Image Map Pro plugin is not found in the installation
  2. Identify the installed version of Image Map Pro
    In WordPress admin, find Image Map Pro in the plugins list and read the version number from the plugin row. Alternatively, inspect the main plugin file header (typically in /wp-content/plugins/image-map-pro/ or similar path) for the 'Version' field
    Affected if Unable to determine the version number
  3. Compare your version against the vulnerable range
    Compare the installed version number to 5.6.9 - any version below 5.6.9 (such as 5.6.8, 5.6.7, etc.) is in the vulnerable range
    Affected if Installed version is lower than 5.6.9 (e.g., 5.6.8, 5.6.0, 4.x)
  4. Confirm the plugin is active
    In WordPress admin Plugins page, verify that Image Map Pro shows as 'Active' rather than 'Inactive'
    Affected if Plugin is active and version is below 5.6.9

You are affected if the Image Map Pro WordPress plugin is installed, active, and running at a version lower than 5.6.9.

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 5.6.9 or later
Fixed in 5.6.9
Interim mitigation

Update Image Map Pro plugin to version 5.6.9 or later, which should include proper nonce verification for admin actions to prevent CSRF attacks. Until updated, avoid clicking untrusted links while logged into WordPress admin.

Recommended fix High confidence

5.6.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Image Map Pro for WordPress - Interactive SVG Image Map Builder' plugin
  4. Check if the current version is below 5.6.9
  5. If update available, click 'Update Now' to upgrade to version 5.6.9
  6. Alternatively, go to Dashboard > Updates and select the plugin to update
  7. After update, verify the plugin version shows 5.6.9 or higher

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

Fix this in Interactive Svg Image Map Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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