CVE-2026-1165

Popup Box <= 6.1.1 - Cross-Site Request Forgery to Popup Status Change

2026-01-30 00:00
w41bu1

Strategic Overview

Status
Patched in 6.1.2
Affected Plugin
Popup Box – Create Countdown, Coupon, Video, Contact Form Popups
Affected Version
<= 6.1.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-1165
View all Popup Box – Create Countdown, Coupon, Video, Contact Form Popups vulnerabilities

At a glance

CVE-2026-1165 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Popup Box WordPress plugin, affecting versions <= 6.1.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.1.2; sites on affected versions should update now. Disclosed January 2026, reported by w41bu1.

Vulnerability Overview

The Popup Box plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.1.1. This is due to a flawed nonce implementation in the 'publish_unpublish_popupbox' function that verifies a self-created nonce rather than one submitted in the request. This makes it possible for unauthenticated attackers to change the publish status of popups via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Popup Box <= 6.1.1 carries this weakness at publish_unpublish_popupbox, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Popup Box the fix is 6.1.2: builds <= 6.1.1 are affected, anything from 6.1.2 onward is not.

Remediation

Update to version 6.1.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Popup Box: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Popup Box 6.1.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1165https://www.wordfence.com/threat-intel/vulnerabilities/id/585a9eb4-f394-4cb2-9050-659171a994d9https://nvd.nist.gov/vuln/detail/CVE-2026-1165

Related records

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