dbcve.org
FoogalleryWordPress extension · Fooplugins

CVE-2024-12119

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-08
Fix available
A fix is available. Upgrade to 2.4.30 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 FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry & Carousel plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the default_gallery_title_size parameter in all versions up to, and including, 2.4.29 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with granted gallery and album creator roles, 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

Stored XSS vulnerability in FooGallery plugin allows authenticated users with gallery/album creator roles to inject arbitrary JavaScript via the default_gallery_title_size parameter due to insufficient input sanitization and output escaping.

MitigationUpgrade to the latest version of FooGallery to obtain the patch that adds proper sanitization and output escaping for the affected parameter.

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
FoogalleryWordPress extension
Affected:< 2.4.30

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. Confirm FooGallery plugin installation
    Navigate to WordPress admin dashboard, go to Plugins section, locate Foogallery in the installed plugins list
    Affected if FooGallery is not installed or not found in the plugin list
  2. Identify installed FooGallery version
    In the WordPress Plugins page, check the version number displayed under the FooGallery plugin name
    Affected if The installed version is lower than 2.4.30 (e.g., 2.4.20, 2.4.0, 1.x)
  3. Verify presence of gallery creator roles
    In WordPress admin, go to Users > Roles or check user capabilities. Look for roles with gallery or album creation permissions such as Gallery Creator, Album Creator, or custom roles with foogallery capabilities
    Affected if User roles with gallery/album creation privileges exist in the WordPress installation
  4. Check plugin settings for vulnerable parameter
    Access FooGallery plugin settings (typically under FooGallery > Settings or a similar menu path). Look for any configuration field named default_gallery_title_size, title size, or similar gallery default settings where a numeric size value can be specified
    Affected if The default_gallery_title_size parameter or equivalent title size setting is present and configurable

The environment is affected if FooGallery version is below 2.4.30 AND gallery/album creator roles exist with access to the plugin's settings containing the vulnerable parameter.

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.4.30 or later
Fixed in 2.4.30
Interim mitigation

Upgrade to the latest version of FooGallery to obtain the patch that adds proper sanitization and output escaping for the affected parameter.

Recommended fix High confidence

FooGallery version 2.4.30

  1. Update the FooGallery plugin to version 2.4.30 or later via the WordPress admin dashboard (Plugins > All Plugins > FooGallery > Update Now), or via command line: wp plugin update foogallery

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

Fix this in Foogallery Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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