dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57396

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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 ('Cross-site Scripting') vulnerability in Flintop Free Gifts for WooCommerce free-gifts-for-woocommerce allows Stored XSS.This issue affects Free Gifts for WooCommerce: from n/a through <= 13.1.0.

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 Cross-site Scripting (XSS) vulnerability in Flintop Free Gifts for WooCommerce plugin allows attackers to inject malicious scripts through unsanitized user input that gets stored and rendered in web pages without proper output encoding, affecting versions up to and including 13.1.0.

MitigationUpdate to the latest patched version when released. Until then, implement proper input validation and output encoding (using functions like esc_html(), esc_attr(), sanitize_text_field()) on all user-supplied data before rendering in web pages.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 plugin installation
    Navigate to WordPress admin > Plugins and locate 'Flintop Free Gifts for WooCommerce' or search for 'flintop' in the plugins list. Verify the plugin is active.
    Affected if The plugin is installed and active in WordPress.
  2. Identify installed version
    In the Plugins list, click on the plugin name or view details to find the version number displayed (typically listed below the plugin name). Compare this version to 13.1.0.
    Affected if The installed version is 13.1.0 or lower.
  3. Check for gift configuration data
    Access the plugin settings: typically found under WooCommerce > Free Gifts or a similar menu item. Review any existing gift rules, product selections, or custom text fields where user-supplied data may be stored.
    Affected if Gift rules or configurations exist in the plugin, indicating the feature where unsanitized input could be stored is in use.
  4. Inspect stored gift data in database
    Access the WordPress database via phpMyAdmin or wp-cli. Query the wp_postmeta table for postmeta_key fields related to the plugin (common patterns include 'flintop_free_gift', 'free_gift', or similar prefixes). Examine the meta_value columns for any raw HTML or script tags.
    Affected if Stored meta data contains unescaped HTML or JavaScript characters indicating a lack of output encoding.

You are affected if the Flintop Free Gifts for WooCommerce plugin is active at version 13.1.0 or lower and gift configuration features have been used, as this creates the conditions for stored XSS to execute.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version when released. Until then, implement proper input validation and output encoding (using functions like esc_html(), esc_attr(), sanitize_text_field()) on all user-supplied data before rendering in web pages.

Recommended fix Moderate confidence

Latest version of Free Gifts for WooCommerce (check WordPress plugin repository for current release)

  1. Check the current version of the Free Gifts for WooCommerce plugin installed on the WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is <= 13.1.0, update the plugin to the latest available version from the WordPress plugin repository
  4. After updating, verify the plugin functions correctly with the WooCommerce store
  5. Review any released security notes or changelogs for the new version
Caveat Review plugin changelog before upgrading to ensure compatibility with current WooCommerce version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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