dbcve.org
Modula Image GalleryWordPress extension · Wpchill

CVE-2024-9416

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-03
Fix available
A fix is available. Upgrade to 2.10.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
The Modula Image Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's bundled FancyBox JavaScript library (versions <= 5.0.36) due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The Modula Image Gallery WordPress plugin contains a stored XSS vulnerability in its bundled FancyBox JavaScript library (versions 5.0.36 and below). Authenticated attackers with contributor-level permissions can inject malicious scripts through unsanitized user-supplied attributes, which persist in the database and execute when other users access affected gallery pages.

MitigationUpdate the Modula Image Gallery plugin to the latest version to obtain a patched FancyBox library, or ensure contributor-level users are restricted from creating/editing galleries until the update is applied.

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
Modula Image GalleryWordPress extension
Affected:< 2.10.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. Identify Modula Image Gallery plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Modula Image Gallery' and note the installed version number
    Affected if Version is displayed as lower than 2.10.2 (for example, 2.10.1, 2.9.8, etc.)
  2. Confirm FancyBox library inclusion
    Check the plugin files for the bundled FancyBox JavaScript library (typically in /js/ or /assets/ folder within the plugin directory)
    Affected if FancyBox library version 5.0.36 or below is bundled with the plugin
  3. Verify contributor-level access to galleries
    Navigate to WordPress admin > Users > Roles, or check if contributor-role users can access the Modula gallery creation interface at /wp-admin/post-new.php?post_type=modula-gallery
    Affected if Contributor-level users have permission to create or edit galleries
  4. Inspect existing gallery configurations for suspicious content
    Query the WordPress database: SELECT ID, post_title, meta_value FROM wp_posts p JOIN wp_postmeta m ON p.ID = m.post_id WHERE post_type = 'modula-gallery' AND meta_key LIKE '%fancybox%' or inspect gallery shortcodes in post content for encoded script tags
    Affected if Gallery configurations contain unsanitized HTML/script attributes or encoded malicious scripts

The environment is affected if Modula Image Gallery plugin version is below 2.10.2 AND contributor-level users have access to create or edit galleries, or if existing galleries already contain injected malicious scripts.

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

Update the Modula Image Gallery plugin to the latest version to obtain a patched FancyBox library, or ensure contributor-level users are restricted from creating/editing galleries until the update is applied.

Recommended fix High confidence

Modula Image Gallery version 2.10.2 or later

  1. Create a full backup of your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Modula Image Gallery plugin in the list
  4. Click the 'Update now' link if an update is available, or go to Plugins > Add New > Upload Plugin to manually upload version 2.10.2 or later
  5. Verify the plugin updated successfully by checking the version number in the plugins list
  6. Clear any caching plugins or server-side caches
  7. Test that the gallery functionality works correctly with existing galleries

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

Fix this in Modula Image Gallery Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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