Back Button WidgetWordPress extension · Wpfactory
CVE-2025-48252
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 Back Button Widget back-button-widget allows Stored XSS.This issue affects Back Button Widget: from n/a through <= 1.6.8.
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 confidenceThe WPFactory Back Button Widget plugin fails to properly sanitize user-supplied input during web page generation, allowing authenticated attackers to inject malicious JavaScript code that gets stored in the database and executed in the browsers of users viewing affected pages.
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
Back Button WidgetWordPress extension
<= 1.6.8CVSS 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 plugin installationCheck if the WPFactory Back Button Widget plugin is installed by looking in wp-content/plugins/ for a folder containing 'back-button-widget' or checking the WordPress plugins admin page.Affected if The plugin is present in the WordPress installation
-
Check installed versionRead the plugin header in the main PHP file (usually wp-content/plugins/back-button-widget/*.php) to find the Version comment, or check the plugins admin list in WordPress.Affected if Version is 1.6.8 or lower
-
Identify plugin settings storageCheck the WordPress database wp_options table for rows where option_name contains 'back_button_widget' or similar patterns using: SELECT * FROM wp_options WHERE option_name LIKE '%back_button%';Affected if Plugin settings are stored in the database
-
Inspect stored values for unsanitized inputExamine the values found in the wp_options query. Look for any HTML, script tags, or JavaScript event handlers (onclick, onerror, etc.) that were not properly escaped.Affected if Stored values contain unescaped HTML or JavaScript code
-
Verify user access to plugin settingsCheck which user roles have access to the plugin settings page by examining capability checks in the plugin code or testing access with low-privilege accounts (subscriber, contributor).Affected if Low-privilege users (subscriber, contributor, or author) can access and modify plugin settings
You are affected if the plugin is installed with version 1.6.8 or lower AND low-privilege users can access plugin settings AND malicious script tags or JavaScript event handlers are found in the stored plugin options.
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 which should include proper input sanitization and output encoding. Until then, restrict low-privilege user access to the affected plugin settings.
Fix this in Back Button Widget
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48252 — 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-48252 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