dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-12122

MEDIUM · 6.4 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Popup Box – Easily Create WordPress Popups plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'iframeBox' shortcode in all versions up to, and including, 3.2.12 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The Popup Box WordPress plugin up to version 3.2.12 contains a stored XSS vulnerability in its iframeBox shortcode. Authenticated attackers with contributor-level permissions can inject malicious JavaScript through unsanitized shortcode attributes; the payload executes whenever users access pages containing the compromised shortcode.

MitigationUpdate the plugin to version 3.2.13 or later. If no patched version is available, audit and remove any existing iframeBox shortcode usage from content authored by untrusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Popup Box plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate the Popup Box plugin. Check the version number displayed under the plugin name. Alternatively, check the plugin header in the main plugin file (usually in wp-content/plugins/popup-box/popup-box.php) for the Version field.
    Affected if The installed version is 3.2.12 or lower (any version up to and including 3.2.12).
  2. Detect iframeBox shortcode usage
    Search your WordPress database for content containing the iframeBox shortcode. This can be done via SQL query: SELECT * FROM wp_posts WHERE post_content LIKE '%[iframeBox%' AND post_status IN ('publish','draft','pending'); (adjust wp_ prefix if different).
    Affected if The shortcode [iframeBox] is present in any published or editable content.
  3. Inspect shortcode attributes for injection
    Examine the raw post_content for any iframeBox shortcodes found. Look for unusual attribute values such as those containing javascript:, onerror=, onload=, or HTML tags like <script>, <img>, <svg>. Check both quoted and unquoted attribute values.
    Affected if Any iframeBox shortcode contains suspicious characters or patterns commonly used in XSS payloads (e.g., event handlers, script tags, encoded characters).
  4. Review content authors with contributor-level access
    In WordPress admin, go to Users > All Users and identify accounts with the Contributor or Author role. These roles can create and edit posts containing shortcodes.
    Affected if Any user with Contributor, Author, Editor, or Administrator role exists who could have inserted the shortcode, especially if they are untrusted or departed users.

You are affected if the Popup Box plugin version is 3.2.12 or lower AND any page/post contains an iframeBox shortcode with potentially malicious or unsanitized attribute values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.2.13 or later. If no patched version is available, audit and remove any existing iframeBox shortcode usage from content authored by untrusted users.

Recommended fix Moderate confidence

Version 3.2.13 or later of the Popup Box – Easily Create WordPress Popups plugin

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Popup Box – Easily Create WordPress Popups' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.2.13 or later
  5. 5. Verify the update completed successfully
  6. 6. Test the iframeBox shortcode functionality to ensure the plugin still works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12122 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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