dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2022-45850

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 allows Stored XSS.This issue affects Image Map Pro: from n/a before 5.6.9.

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 Nickys Image Map Pro plugin allows attackers to craft malicious requests that, when triggered by an authenticated administrator, injects persistent malicious scripts (Stored XSS) into the application. The lack of anti-CSRF tokens enables attackers to force the admin browser to submit unintended requests that save malicious content to the database, which then executes when other users view the affected content.

MitigationUpdate Image Map Pro to version 5.6.9 or later, which includes proper CSRF token validation and input sanitization to prevent unauthorized stored XSS injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Image Map Pro plugin is installed
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'Image Map Pro' or 'Nickys Image Map Pro' to confirm the plugin is present on the system.
    Affected if The plugin is installed and active on the WordPress site.
  2. Determine installed version of Image Map Pro
    In the WordPress plugins list, locate Image Map Pro and note the version number displayed under the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/image-map-pro/ directory for the 'Version' tag.
    Affected if Version is lower than 5.6.9 (the patched version).
  3. Compare version against vulnerability threshold
    Take the installed version number identified in step 2 and compare it numerically to version 5.6.9. Any version below 5.6.9 (such as 5.6.8, 5.6.7, etc.) is considered vulnerable.
    Affected if Installed version is below 5.6.9.
  4. Inspect admin forms for CSRF protection tokens
    Navigate to the Image Map Pro settings page in WordPress admin. View the HTML source of any forms (create/edit map forms, settings forms) and check for the presence of a nonce token or CSRF token field (typically named '_wpnonce', 'nonce', or similar).
    Affected if Forms lack anti-CSRF token fields or validation is missing.
  5. Check for stored XSS payload in map data
    In WordPress admin, go to Image Map Pro > All Maps, select any map, and inspect the map name, descriptions, or hotspot content for suspicious script tags or encoded JavaScript that was not intentionally added by an administrator.
    Affected if Unexpected script tags or malicious content exists in map data that was not added by the legitimate admin.

The environment is affected if Image Map Pro plugin is installed with a version lower than 5.6.9 and the plugin admin forms lack CSRF token protection, allowing unauthorized stored XSS injection.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Image Map Pro to version 5.6.9 or later, which includes proper CSRF token validation and input sanitization to prevent unauthorized stored XSS injection.

Recommended fix Moderate confidence

Image Map Pro 5.6.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Image Map Pro' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 5.6.9
  5. Verify the plugin version shows 5.6.9 or later after updating

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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