Plugins · popad · data as of 2026-11-04
Is PopAd safe? Known vulnerabilities and latest version
- Status
- Closed 2025-09-01
- Known issues on record
- 2
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate popad && wp plugin delete popad
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.
medium 4.4 CVE-2025-60175 · published 2026-06-15
Server-side request forgery (SSRF) in PopAd (1.0.4 and older)
- Affected
- 1.0.4 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Administrator Server Side Request Forgery (SSRF) in PopAd <= 1.0.4 versions.
medium 5.3 CVE-2025-9616 · published 2025-09-04
Cross-site request forgery (CSRF) in PopAd (1.0.4 and older)
- Affected
- 1.0.4 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The PopAd plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.4. This is due to missing or incorrect nonce validation on the PopAd_reset_cookie_time function. This makes it possible for unauthenticated attackers to reset cookie time settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Recent activity
- 2025-09-01 — closed on wordpress.org (Author Request).
- 2026-06-15 — Server-side request forgery (SSRF) disclosed (CVE-2025-60175), fix version not stated.
- 2025-09-04 — Cross-site request forgery (CSRF) disclosed (CVE-2025-9616), fix version not stated.
Get an email when PopAd has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for PopAd (popad) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Server-side request forgery (SSRF) (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/popad (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/popad"><img src="https://laskyr.com/plugins/popad/badge.svg" alt="PopAd vulnerability status"></a>