Image Hover Effects For Elementor With Lightbox And FlipboxWordPress extension · Oxilab

CVE-2024-37546

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-06
Fix available
A fix is available. Upgrade to after 3.0.2 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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in biplob018 Image Hover Effects - Caption Hover with Carousel allows Stored XSS.This issue affects Image Hover Effects - Caption Hover with Carousel: from n/a through 3.0.2.

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

Stored XSS vulnerability in the Image Hover Effects - Caption Hover with Carousel WordPress plugin (versions through 3.0.2). The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing attackers to inject malicious JavaScript code that executes when other users view the affected content.

MitigationUpdate the plugin to the latest version immediately. If no patched version is available, disable the plugin until a fix is released. Consider implementing additional output escaping as a temporary workaround.

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 Effects For Elementor With Lightbox And FlipboxWordPress extension
Affected:<= 3.0.2

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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Image Hover Effects - Caption Hover with Carousel' or 'Oxilab Image Hover Effects For Elementor With Lightbox And Flipbox'. Note if it appears in the list.
    Affected if The plugin appears in the installed plugins list.
  2. Check the installed version number
    In the Plugins list, find the plugin and look at the version number displayed below the plugin name. Compare this version against the affected range (3.0.2 and earlier).
    Affected if The installed version is 3.0.2 or any earlier version.
  3. Identify if the plugin functionality is actively used
    Check your pages, posts, or widgets for any Image Hover Effects shortcodes or blocks that display the plugin's content. Look for any published content using this plugin's features.
    Affected if The plugin is installed and actively rendering content on the site.
  4. Inspect input fields used by the plugin
    If you have access to the plugin settings or any frontend forms it provides, identify input fields where users can enter text that gets stored and displayed (such as captions, titles, or descriptions for image hover effects).
    Affected if User-supplied input fields exist and are accessible without admin-only restrictions.

You are affected if the plugin is installed at version 3.0.2 or earlier and is actively displaying content that accepts user-supplied input.

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

Update the plugin to the latest version immediately. If no patched version is available, disable the plugin until a fix is released. Consider implementing additional output escaping as a temporary workaround.

Fix this in Image Hover Effects For Elementor With Lightbox And Flipbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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