CVE-2025-12122

Popup Box – Easily Create WordPress Popups <= 3.2.12 - Authenticated (Contributor+) Stored Cross-Site Scripting

2026-02-17 16:37
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 3.2.13
Affected Version
<= 3.2.12
CVSS
6.4Medium
Weakness type
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
CVE
CVE-2025-12122
View all Popup Box – Easily Create WordPress Popups vulnerabilities

At a glance

CVE-2025-12122 is a medium-severity Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in the Popup Box WordPress plugin, affecting versions <= 3.2.12. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.2.13; sites on affected versions should update now. Disclosed February 2026, reported by Jonas Benjamin Friedli.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

Remediation

Update to version 3.2.13, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Popup Box 3.2.13 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C