LiveActive security incident?Get immediate response
CVE Record

CVE-2024-33639: WordPress PopupAlly plugin <= 2.1.1 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in AccessAlly PopupAlly allows Stored XSS.This issue affects PopupAlly: from n/a through 2.1.1.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-33639 is a stored cross-site scripting issue in the WordPress PopupAlly plugin through version 2.1.1. A highly privileged user could save unsafe input that later runs in another user’s browser. Business risk is moderate because exploitation requires high privileges and user interaction, but impact can cross trust boundaries in WordPress administration.

Executive priority

Treat as a moderate WordPress application risk. It should be handled in normal vulnerability remediation cycles, faster for externally facing sites, client portals, or environments with many administrators. Prioritize inventory first because exposure depends on plugin presence and version.

Technical view

The CVE describes CWE-79 improper input neutralization during web page generation in AccessAlly PopupAlly. CVSS 3.1 is 5.9 with AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L. The public bundle identifies PopupAlly through 2.1.1 as affected, with no confirmed active exploitation and no specific fix version stated.

Likely exposure

Exposure is likely limited to WordPress installations running PopupAlly version 2.1.1 or earlier. Risk is higher where many high-privilege users can administer plugin content or settings. Sites not using PopupAlly are not exposed based on the provided sources.

Exploitation context

No KEV listing or cited source confirms active exploitation. The CVSS vector indicates network reachability, low attack complexity, high privileges required, and required victim interaction. The stored nature means malicious content may persist until removed, but source detail is sparse.

Researcher notes

Public details are limited to stored XSS, affected versions through 2.1.1, and CVSS metadata. Do not assume unauthenticated exploitation or a specific vulnerable field from the provided bundle. Validate with authorized testing and vendor advisory review rather than inferred payload behavior.

Mitigation direction

  • Inventory WordPress sites for PopupAlly and record installed versions.
  • Check AccessAlly, WordPress.org, and Patchstack guidance for a fixed release.
  • Update PopupAlly if a vendor-supported fixed version is available.
  • Restrict plugin administration to trusted high-privilege users.
  • Disable or remove the plugin if no supported fix is available.

Validation and detection

  • Confirm whether PopupAlly version is 2.1.1 or earlier.
  • Review plugin roles and who can modify PopupAlly settings or content.
  • Check security advisories for any fixed version or workaround.
  • Inspect PopupAlly-managed content for unexpected scripts or unauthorized changes.
  • Verify changes in staging before production rollout where possible.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-33639 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2024-33639Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AccessAllyPopupAllypopupally, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.