Free Shipping BarWordPress extension · Wpfactory
CVE-2025-48253
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPFactory Free Shipping Bar: Amount Left for Free Shipping for WooCommerce amount-left-free-shipping-woocommerce allows Stored XSS.This issue affects Free Shipping Bar: Amount Left for Free Shipping for WooCommerce: from n/a through <= 2.4.6.
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 confidenceThis is a stored XSS (Cross-site Scripting) vulnerability in the WPFactory Free Shipping Bar plugin for WooCommerce. The plugin fails to properly sanitize user-supplied input, allowing malicious JavaScript code to be stored in the database and executed when administrators or customers view the affected interface.
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
Free Shipping BarWordPress extension
<= 2.4.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedNavigate to WordPress admin > Plugins and look for 'Free Shipping Bar' by Wpfactory or WPFactory, or use WP-CLI: wp plugin list --name='free-shipping-bar'Affected if The plugin is installed and active
-
Check the installed versionIn WordPress admin > Plugins, find the Free Shipping Bar plugin and look at the version number displayed, or use WP-CLI: wp plugin get free-shipping-bar --field=versionAffected if Version is 2.4.6 or lower
-
Identify plugin input fieldsNavigate to the plugin settings page (usually WooCommerce > Free Shipping Bar or under the plugin menu) and locate any text input fields where users can enter custom messages, labels, or contentAffected if The plugin provides user-editable text fields (message text, labels, etc.) that accept and store input
-
Inspect stored data for unsanitized contentCheck the WordPress database wp_options table for entries related to the plugin (look for option_name containing 'shipping_bar' or 'alg_wc_shipping_bar') and examine if the stored values contain raw HTML or script tags without escapingAffected if Stored option values contain raw HTML, script tags, or unescaped user input
You are affected if the WPFactory Free Shipping Bar plugin is installed at version 2.4.6 or lower and contains user-editable input fields that store unsanitized content.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to the latest version beyond 2.4.6. If no patch is available, disable the plugin until a secure version is released. Additionally, audit all user inputs handled by the plugin for proper sanitization and output encoding.
Fix this in Free Shipping Bar
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48253 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48253 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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