Bbs E PopupWordPress extension · Bbsetheme
CVE-2023-34174
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in BBS e-Theme BBS e-Popup plugin <= 2.4.5 versions.
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 confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the BBS e-Popup plugin for WordPress (versions 2.4.5 and below). Attackers can inject malicious JavaScript through unsanitized user input that gets reflected back in the web page response.
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
Bbs E PopupWordPress extension
<= 2.4.5CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate the installed version of the BBS e-Popup pluginIn WordPress admin, go to Plugins > Installed Plugins and look for 'Bbsetheme Bbs E Popup' in the list. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file (usually in /wp-content/plugins/bbs-e-popup/) for the 'Version' header in the plugin comment block, or run: grep -i 'Version:' /wp-content/plugins/bbs-e-popup/*.php | head -5Affected if The displayed version is 2.4.5 or lower, or if no version is listed but the plugin is present in the plugins directory with no available update
-
Confirm the plugin is active on the siteIn WordPress admin, go to Plugins > Installed Plugins and check if 'Bbsetheme Bbs E Popup' has an 'Active' status, or run: wp plugin list --status=active --format=csv | grep -i 'bbs.*popup'Affected if The plugin is currently active (unauthenticated means the vulnerability is accessible without login)
-
Identify the vulnerable endpointThis is a reflected XSS vulnerability. The plugin reflects user-supplied input back into the page without sanitization. Typical XSS parameters include 'message', 'id', 'popup_id', or similar. Check any publicly accessible URL that includes the plugin's slug or functionality (often /?bps= or similar query parameters). Use browser developer tools or curl to inspect the HTTP response when supplying a test string like <script>alert(1)</script> in common parameter names.Affected if The HTTP response contains the unsanitized test string literally (not encoded or stripped), indicating the input is reflected without proper output encoding
You are affected if the BBS e-Popup plugin version is 2.4.5 or lower and the plugin is installed and active on your WordPress site.
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 BBS e-Popup plugin to a version newer than 2.4.5, or remove the plugin if no patched version is available. Alternatively, disable the plugin until an update is released.
Fix this in Bbs E Popup
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34174 — 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-34174 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