dbcve.org
FoogalleryWordPress extension · Fooplugins

CVE-2024-2081

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 2.4.15 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 Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the foogallery_attachment_modal_save action in all versions up to, and including, 2.4.14 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-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 FooGallery WordPress plugin up to version 2.4.14 contains a stored XSS vulnerability in the foogallery_attachment_modal_save action. Authenticated attackers with author-level permissions can inject malicious JavaScript through insufficiently sanitized input, which persists in the database and executes when other users view affected gallery pages.

MitigationUpgrade to FooGallery version 2.4.15 or later, which includes proper input sanitization and output escaping for the affected action.

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.15

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 FooGallery plugin installation and version
    Check the installed FooGallery version in WordPress under Plugins > Installed Plugins, or inspect the plugin header in foogallery.php file
    Affected if FooGallery version is installed and is lower than 2.4.15
  2. Identify users with author-level or higher permissions
    In WordPress admin, navigate to Users > All Users and review user roles; authors and above can access the vulnerable action
    Affected if There are user accounts with author, editor, or administrator roles who could access the foogallery_attachment_modal_save action
  3. Inspect gallery database entries for suspicious script content
    Query the WordPress database (wp_postmeta table, or wherever Foogallery stores gallery metadata) for any gallery entries containing script tags, javascript:, or on* event handlers
    Affected if Database contains gallery metadata with unsanitized HTML or JavaScript that could indicate exploitation
  4. Review recent activity logs for foogallery_attachment_modal_save
    Check WordPress activity logs, server access logs, or security plugins for recent calls to admin-ajax.php with action=foogallery_attachment_modal_save, especially with unexpected input
    Affected if Unusual or suspicious requests to the foogallery_attachment_modal_save action are present in logs

You are affected if FooGallery version is below 2.4.15 AND you have users with author-level or higher permissions who could have triggered the vulnerable action, or if malicious script content is found stored in gallery database entries.

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.15 or later
Fixed in 2.4.15
Interim mitigation

Upgrade to FooGallery version 2.4.15 or later, which includes proper input sanitization and output escaping for the affected action.

Recommended fix High confidence

Foogallery 2.4.15

  1. 1. Log in to the WordPress admin dashboard with an account having administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the Foogallery plugin in the list.
  4. 4. If an update is available, click the 'Update Now' link next to the Foogallery plugin.
  5. 5. Alternatively, go to Dashboard > Updates and check for available updates, then update Foogallery.
  6. 6. After updating, verify the plugin version is 2.4.15 or higher by checking the plugin list.

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

Fix this in Foogallery Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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