dbcve.org
FoogalleryWordPress extension · Fooplugins

CVE-2023-6747

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-03
Fix available
A fix is available. Upgrade to 2.4.6 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 custom attributes in all versions up to, and including, 2.3.3 due to insufficient input sanitization and output escaping. This makes it possible for contributors 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 is vulnerable to stored XSS in its custom attributes due to insufficient input sanitization and output escaping. Authenticated users with contributor-level permissions or higher can inject arbitrary JavaScript through custom gallery attributes, which executes when other users view affected pages.

MitigationUpdate FooGallery to version 2.3.4 or later, which includes proper sanitization and output escaping for custom attributes.

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

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 is installed
    Check WordPress admin under Plugins > Installed Plugins, or inspect the plugin directory for foogallery
    Affected if FooGallery plugin is present in the WordPress installation
  2. Determine installed FooGallery version
    View plugin details in WordPress admin or read the main plugin file header for the Version field
    Affected if Version is less than 2.4.6
  3. Identify galleries using custom attributes
    Access FooGallery settings and review individual gallery configurations for custom attribute fields
    Affected if Any gallery has custom attributes configured and the plugin version is below 2.4.6
  4. Inspect custom attribute values for potential XSS payloads
    Examine stored custom attribute values in the gallery database or export gallery settings to review raw data
    Affected if Custom attribute values contain unsanitized script tags, event handlers, or javascript: URIs

A user is affected if FooGallery version is below 2.4.6 AND custom gallery attributes are in use with unsanitized input that could execute JavaScript.

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.6 or later
Fixed in 2.4.6
Interim mitigation

Update FooGallery to version 2.3.4 or later, which includes proper sanitization and output escaping for custom attributes.

Recommended fix High confidence

FooGallery version 2.4.6

  1. Backup the WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find the FooGallery plugin and click 'Update Now' to upgrade to version 2.4.6 or later
  4. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  5. Verify the plugin is updated to version 2.4.6 or higher after the update completes
  6. Clear any caching plugins if used and test that the gallery functionality works correctly

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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