Change Add To Cart Button Text For WoocommerceWordPress extension · Wpfactory
CVE-2025-48254
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 Change Add to Cart Button Text for WooCommerce add-to-cart-button-labels-for-woocommerce allows Stored XSS.This issue affects Change Add to Cart Button Text for WooCommerce: from n/a through <= 2.2.2.
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 confidenceStored XSS vulnerability in the WPFactory 'Change Add to Cart Button Text for WooCommerce' plugin allows authenticated attackers to inject malicious JavaScript through the button text settings field. The injected payload is stored in the database and executes when WooCommerce displays the modified add-to-cart buttons in the storefront.
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
Change Add To Cart Button Text For WoocommerceWordPress extension
<= 2.2.2CVSS 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.
-
Check plugin version installedNavigate to WordPress admin > Plugins and locate 'Change Add to Cart Button Text for WooCommerce' by WPFactory. Compare the installed version number to the affected range: <= 2.2.2Affected if The installed version is 2.2.2 or lower
-
Verify WooCommerce is activeConfirm WooCommerce plugin is installed and active in WordPress admin > Plugins. The XSS only triggers when WooCommerce displays add-to-cart buttons.Affected if WooCommerce is active and the vulnerable plugin version is installed
-
Inspect plugin settings for suspicious contentGo to WooCommerce > Settings > Products > Add to Cart Button Text (or the plugin's settings page if accessible). Examine the button text fields for any unexpected HTML, script tags, or JavaScript code.Affected if The button text settings contain script tags, javascript:, or other suspicious markup
-
Check database for stored XSS payloadsQuery the WordPress options table (wp_options) for option_name containing 'wpfctb' or the plugin's option prefix. Look for option_value fields containing raw HTML, script elements, or event handlers like onerror, onload.Affected if The stored option values contain unescaped HTML or JavaScript code
A user is affected if they have plugin version 2.2.2 or lower, WooCommerce is active, and either the settings contain malicious payloads or untrusted users have access to the plugin settings.
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 version 2.2.3 or later which includes proper input sanitization. Until patched, restrict access to the plugin settings to trusted administrators only.
Fix this in Change Add To Cart Button Text For Woocommerce
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-48254 — 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-48254 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