Popup AnythingWordPress extension · Essentialplugin
CVE-2021-24883
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 · uneditedThe Popup Anything WordPress plugin before 2.0.4 does not escape the Link Text and Button Text fields of Popup, which could allow users with a role as low as Contributor to perform Cross-Site Scripting attacks
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 confidenceThe Popup Anything WordPress plugin before version 2.0.4 fails to escape the Link Text and Button Text fields when rendering Popups, allowing authenticated users with Contributor role or higher to inject malicious JavaScript code that executes in the browsers of other users viewing the popup.
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
Popup AnythingWordPress extension
< 2.0.4CVSS 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 Popup Anything plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Popup Anything' or 'Popup Anything by Essential Plugin' in the list of active pluginsAffected if The plugin appears in the installed plugins list and is active
-
Determine installed plugin versionIn the Plugins list, click on the plugin name or view the plugin file header at wp-content/plugins/popup-anything-on-click/popup-anything-on-click.php to read the Version field from the plugin comment headerAffected if The displayed version number is less than 2.0.4 (for example, 2.0.3, 2.0.2, etc.)
-
Identify configured popupsNavigate to the Popup Anything settings page in the WordPress admin (usually under a menu item like Popup Anything or a similar section), and review the list of created popupsAffected if Any popups have been created and saved in the system
-
Inspect Link Text and Button Text fieldsEdit each existing popup and examine the 'Link Text' and 'Button Text' input fields for any content - these are the fields that were not properly escaped before version 2.0.4Affected if Any popup contains JavaScript or HTML code (such as <script> tags, event handlers like onmouseover, or javascript: URIs) in these text fields, indicating potential exploitation
You are affected if the Popup Anything plugin is installed with a version earlier than 2.0.4 and any popups exist with potentially malicious content in the Link Text or Button Text fields.
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.
dbcve · scoped2.0.4
Update Popup Anything plugin to version 2.0.4 or later which implements proper output escaping. If immediate update is not feasible, disable the plugin until the patch can be applied.
2.0.4
- Backup your WordPress site database and files before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate the 'Popup Anything' plugin in the list
- Click 'Update now' if an update is available, or manually upload version 2.0.4 of the plugin
- Verify the plugin version shows 2.0.4 or higher after update
- Test popup functionality to ensure the update did not break existing features
- Clear any caching plugins or server-side caches
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Popup Anything
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-2021-24883 — 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-2021-24883 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