dbcve.org
Hover ImageWordPress extension · Hover Image Project

CVE-2022-47611

HIGH · 8.8 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to after 1.4.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) vulnerability in Julian Weinert // cs&m Hover Image plugin <= 1.4.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 the Hover Image WordPress plugin affecting versions 1.4.1 and below. The flaw allows attackers to trick authenticated administrators into performing unintended actions via maliciously crafted requests, potentially leading to configuration changes or data manipulation.

MitigationUpdate the Hover Image plugin to a version beyond 1.4.1 once a patch is released by the vendor; until then, enforce SameSite cookies on session cookies and educate administrators about not clicking untrusted links while logged into the WordPress admin panel.

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
Hover ImageWordPress extension
Affected:<= 1.4.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. Check Hover Image plugin version via WordPress admin
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'Hover Image' in the list, and read the version number displayed below the plugin name
    Affected if The version displayed is 1.4.1 or lower
  2. Check Hover Image plugin version via WP-CLI
    Run command: `wp plugin list --slug=hover-image --format=json` or `wp plugin get hover-image` if the plugin slug is 'hover-image'
    Affected if The version field in the output shows 1.4.1 or lower
  3. Check plugin version from source files
    Navigate to /wp-content/plugins/hover-image/ directory, open the main plugin PHP file (commonly hover-image.php or similar), and locate the 'Version' header in the plugin comment block
    Affected if The Version header shows 1.4.1 or lower
  4. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the Hover Image plugin shows as 'Active'
    Affected if The plugin is active and version is 1.4.1 or lower

You are affected if the Hover Image WordPress plugin is installed, active, and the version is 1.4.1 or below, since an authenticated administrator session could be exploited via CSRF requests.

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

Update the Hover Image plugin to a version beyond 1.4.1 once a patch is released by the vendor; until then, enforce SameSite cookies on session cookies and educate administrators about not clicking untrusted links while logged into the WordPress admin panel.

Fix this in Hover Image Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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