Custom Popup BuilderWordPress extension · Custom Popup Builder Project
CVE-2022-28612
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 Access Control vulnerability leading to multiple Authenticated (contributor or higher user role) Stored Cross-Site Scripting (XSS) vulnerabilities in Muneeb's Custom Popup Builder plugin <= 1.3.1 at WordPress.
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 confidenceThis is an Improper Access Control vulnerability in Muneeb's Custom Popup Builder WordPress plugin (versions 1.3.1 and below). Authenticated users with contributor-level permissions or higher can inject malicious JavaScript through the popup builder functionality, which gets stored in the database and executed when other users view the affected popups.
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
Custom Popup BuilderWordPress extension
<= 1.3.1CVSS 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 Custom Popup Builder plugin is installedLocate the plugin in WordPress under Plugins > Installed Plugins, or inspect the plugin directory at wp-content/plugins/custom-popup-builder/ and check the main plugin file header for the Version fieldAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionRead the Version number from the plugin header in custom-popup-builder.php or from the Plugins admin page in WordPressAffected if The version number is 1.3.1 or lower
-
Identify users with contributor-level or higher accessNavigate to Users > All Users in WordPress admin and review the Role column, or query the wp_usermeta table for users with roles including contributor, author, editor, or administratorAffected if Any user account exists with contributor, author, editor, or administrator role (these roles can potentially exploit the vulnerability)
-
Inspect stored popup content for suspicious scriptsQuery the wp_posts table where post_type is related to popups (often 'popup' or 'cpb_popup'), or check the database for any script tags, javascript: URIs, or onload/onerror event handlers in popup post contentAffected if Any popup post contains <script> tags, javascript: pseudo-protocol, or event handlers like onload/onerror in the post_content field
A user is affected if the Custom Popup Builder plugin version is 1.3.1 or lower AND there are contributor-level or higher users present in the WordPress installation who could have injected malicious scripts into popup 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 Muneeb's Custom Popup Builder plugin to version 1.3.2 or later. Additionally, review user roles and capabilities to ensure untrusted users have minimal permissions.
Fix this in Custom Popup Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28612 — 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-2022-28612 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