CVE-2024-56025: WordPress AdWork Media EZ Content Locker plugin <= 3.0 - Reflected Cross Site Scripting (XSS) vulnerability
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in adworkmedia AdWork Media EZ Content Locker adwork-media-ez-content-locker allows Reflected XSS.This issue affects AdWork Media EZ Content Locker: from n/a through <= 3.0.
Security readout for executives and security teams
Plain-English summary
CVE-2024-56025 is a reflected cross-site scripting issue in the WordPress AdWork Media EZ Content Locker plugin through version 3.0. An attacker would need a user to interact with a crafted link or page, but successful exploitation could affect the user’s browser session and site trust.
Executive priority
Prioritize within normal high-severity web application remediation. The issue can affect user sessions and site integrity, but available evidence does not establish active exploitation or unauthenticated direct compromise without user interaction.
Technical view
The issue is CWE-79 improper input neutralization during webpage generation. The published CVSS 3.1 score is 7.1, with network attack vector, low complexity, no privileges required, and user interaction required. The vulnerability affects adwork-media-ez-content-locker through version 3.0.
Likely exposure
Exposure is limited to WordPress sites that have the AdWork Media EZ Content Locker plugin installed at version 3.0 or earlier. Public-facing WordPress sites are the main concern because reflected XSS can be triggered through user interaction.
Exploitation context
The supplied sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires user interaction and no attacker authentication. Evidence is incomplete on exploit availability, affected endpoints, and vendor patch status.
Researcher notes
Sources identify reflected XSS only, not stored XSS or remote code execution. Do not assume endpoint details, exploit maturity, or patch availability from the provided evidence. Validation should focus on asset inventory, version confirmation, and vendor advisory review.
Mitigation direction
Inventory WordPress sites for adwork-media-ez-content-locker installations.
Check plugin version and treat version 3.0 or earlier as affected.
Consult vendor or Patchstack guidance for a fixed or safe version.
Disable or remove the plugin if no maintained safe version is available.
Prioritize remediation on sites used by administrators or authenticated users.
Validation and detection
Confirm whether the plugin is installed in WordPress admin or filesystem.
Record the installed plugin version for each WordPress site.
Check whether any instance is version 3.0 or earlier.
Review available vendor or Patchstack advisories for current remediation status.
Document business ownership before disabling production functionality.
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.
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.
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.