VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 3 known issues Latest disclosed May 20, 2024

PopupAlly Vulnerabilities

Review known vulnerability records for the WordPress plugin PopupAlly (`popupally`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2024-34796, CVE-2024-33639 and CVE-2024-23520, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
3
High or Critical
0
Patch Coverage
100%
Last Updated
May 29, 2024
Related Security Guides

Use these guides while reviewing PopupAlly fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize PopupAlly remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
3
1. Match the Package
Confirm the installed WordPress plugin slug is popupally before acting on any CVE from this cluster.
2. Sort by Severity
Start with 0 high or critical records, then review medium and unrated findings with public references.
3. Check Patch Evidence
3 records include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2024-34796 Medium
Stored Cross-Site Scripting remediation for PopupAlly

Affected range: Versions up to 2.1.1. Fixed version: 2.1.2.

CVE-2024-33639 Medium
Stored Cross-Site Scripting remediation for PopupAlly

Affected range: Versions up to 2.1.1. Fixed version: 2.1.2.

CVE-2024-23520 Medium
Cross-Site Request Forgery remediation for PopupAlly

Affected range: Versions up to 2.1.0. Fixed version: 2.1.1.

Priority CVE Quick Links

Fast paths into PopupAlly CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
3
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2024-34796
PopupAlly <= 2.1.1 - Authenticated (Administrator+) Stored Cross-Site Scripting
 Stored Cross-Site Scripting Versions up to 2.1.1 2.1.2 CVSS 4.4
CVE-2024-33639
PopupAlly <= 2.1.1 - Authenticated (Admin+) Stored Cross-Site Scripting
 Stored Cross-Site Scripting Versions up to 2.1.1 2.1.2 CVSS 4.4
CVE-2024-23520
PopupAlly <= 2.1.0 - Cross-Site Request Forgery via optin_submit_callback
 Cross-Site Request Forgery Versions up to 2.1.0 2.1.1 CVSS 4.3
CVE-2024-34796 Medium 2.1.2
CVE-2024-34796 PopupAlly Stored Cross-Site Scripting

PopupAlly <= 2.1.1 - Authenticated (Administrator+) Stored Cross-Site Scripting

CVE-2024-33639 Medium 2.1.2
CVE-2024-33639 PopupAlly Stored Cross-Site Scripting

PopupAlly <= 2.1.1 - Authenticated (Admin+) Stored Cross-Site Scripting

CVE-2024-23520 Medium 2.1.1
CVE-2024-23520 PopupAlly Cross-Site Request Forgery

PopupAlly <= 2.1.0 - Cross-Site Request Forgery via optin_submit_callback

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for PopupAlly so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
3 records include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 0 high severity findings.
Recent CVEs
CVE-2024-34796, CVE-2024-33639 and CVE-2024-23520
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for PopupAlly

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2024-34796
CVE-2024-34796: PopupAlly <= 2.1.1 - Authenticated (Administrator+) Stored Cross-Site Scripting

The PopupAlly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level...

Published
May 20, 2024
Patched Release
2.1.2
Affected Versions
Versions up to 2.1.1
Next Step
Update to 2.1.2 or newer if supported.
Review CVE-2024-34796 fixed version details Open CVE Reference
Plugin Medium Patched: Yes CVE-2024-33639
CVE-2024-33639: PopupAlly <= 2.1.1 - Authenticated (Admin+) Stored Cross-Site Scripting

The PopupAlly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level...

Published
Apr 25, 2024
Patched Release
2.1.2
Affected Versions
Versions up to 2.1.1
Next Step
Update to 2.1.2 or newer if supported.
Review CVE-2024-33639 fixed version details Open CVE Reference
Plugin Medium Patched: Yes CVE-2024-23520
CVE-2024-23520: PopupAlly <= 2.1.0 - Cross-Site Request Forgery via optin_submit_callback

The PopupAlly plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.0. This is due to missing or incorrect nonce validation on the 'optin_submit_callback' function. This makes it possible for unauthenticated attackers to opt in...

Published
Jan 30, 2024
Patched Release
2.1.1
Affected Versions
Versions up to 2.1.0
Next Step
Update to 2.1.1 or newer if supported.
Review CVE-2024-23520 fixed version details Open CVE Reference