Back Button WidgetWordPress extension · Wpfactory
CVE-2023-51399
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 allows Stored XSS.This issue affects Back Button Widget: from n/a through 1.6.3.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in WPFactory Back Button Widget plugin allows attackers to inject malicious JavaScript code through unsanitized input fields. The injected script executes when site administrators or users view pages containing the compromised widget, potentially leading to session hijacking, credential theft, or malicious redirects.
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.3CVSS 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 files exist in your WordPress installation at wp-content/plugins/back-button-widget/ or similar pathAffected if The plugin directory exists in the wp-content/plugins folder
-
Identify installed versionOpen the main plugin PHP file (usually back-button-widget.php) and locate the version comment or header field at the top of the fileAffected if The version number displayed is 1.6.3 or lower
-
Confirm plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify the WPFactory Back Button Widget is activated, or check the wp_options table for active_plugins entryAffected if The plugin shows as active in WordPress admin or appears in the active_plugins option
-
Check widget configurationNavigate to Appearance > Widgets in WordPress admin and look for the Back Button Widget in any active widget area, or inspect the wp_options table for widget configurations containing 'back-button'Affected if The Back Button Widget is added to a sidebar or widget area and is displayed on live pages
Your environment is affected if WPFactory Back Button Widget is installed, active, and the version is 1.6.3 or lower, with the widget configured on a visible page where unsanitized input could be stored.
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 to the latest version of the WPFactory Back Button Widget plugin which should contain proper input sanitization and output encoding. If no update is available, implement web application firewall rules to block XSS attack patterns until a patch is released.
Fix this in Back Button Widget
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-51399 — 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-2023-51399 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