Image Hover EffectsWordPress extension · Webdevocean

CVE-2023-47552

HIGH · 8.8 CVSS v3.1 Published 2023-11-18
Fix available
A fix is available. Upgrade to after 5.5 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 Labib Ahmed Image Hover Effects – WordPress Plugin.This issue affects Image Hover Effects – WordPress Plugin: from n/a through 5.5.

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 Image Hover Effects WordPress plugin (versions up to 5.5) allows attackers to induce authenticated administrators to perform unintended actions by tricking them into visiting malicious URLs or pages.

MitigationUntil an official patch is released, implement anti-CSRF tokens (nonces) on all state-changing actions in the plugin; alternatively, disable or replace the plugin if no fix becomes available.

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 Hover EffectsWordPress extension
Affected:<= 5.5

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. Confirm plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Image Hover Effects' by Webdevocean, or check the plugin directory for /wp-content/plugins/image-hover-effects/ and inspect the main plugin file header for the Version field
    Affected if Plugin is installed and Version <= 5.5
  2. Identify state-changing admin actions
    Examine the plugin's PHP files (especially main plugin file and any admin-handling files) for form submissions, AJAX handlers, or URL-based actions that modify plugin settings, save options, or manipulate database entries
    Affected if The plugin performs any administrative actions without apparent nonce verification
  3. Check for nonce implementation
    Search the plugin PHP files for WordPress nonce functions: wp_nonce_field, wp_nonce_url, check_admin_referer, check_ajax_referer, or wp_verify_nonce
    Affected if No nonce verification functions are found in files handling admin actions, or nonce checks are missing entirely from state-changing endpoints
  4. Verify nonce usage on forms
    Inspect any HTML forms in the plugin (in admin settings pages, bulk actions, or option saves) by searching for '<form' tags in the PHP files and checking if they include hidden nonce fields
    Affected if Forms that submit to state-changing endpoints lack nonce token fields
  5. Inspect AJAX handlers
    Look for add_action('wp_ajax_*) calls in the plugin and verify if the corresponding handlers call wp_verify_nonce or check_admin_referer before processing requests
    Affected if AJAX endpoints that modify data do not validate nonces

User is affected if the Image Hover Effects plugin (version 5.5 or lower) is installed and the plugin code lacks nonce verification on administrative actions or form submissions that change state.

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

Until an official patch is released, implement anti-CSRF tokens (nonces) on all state-changing actions in the plugin; alternatively, disable or replace the plugin if no fix becomes available.

Fix this in Image Hover Effects 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-2023-47552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-47552 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