Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Softaculous PageLayer pagelayer allows DOM-Based XSS.This issue affects PageLayer: from n/a through <= 1.9.4.
Security readout for executives and security teams
Plain-English summary
CVE-2025-24573 is a DOM-based cross-site scripting flaw in the WordPress PageLayer plugin. On sites using affected versions through 1.9.4, an attacker with low privileges and victim interaction could affect browser-side confidentiality, integrity, and availability. The available sources do not state active exploitation.
Executive priority
Prioritize in normal vulnerability remediation for WordPress properties, especially customer-facing sites with multiple editors or contributors. Escalate if vendor guidance confirms active exploitation or if PageLayer is widely deployed in your environment.
Technical view
The issue is CWE-79 improper input neutralization during page generation in Softaculous PageLayer for WordPress. CVSS 3.1 is 6.5: network reachable, low complexity, low privileges required, user interaction required, changed scope, with low C/I/A impact. Source data names versions through <=1.9.4 as affected.
Likely exposure
Exposure is limited to WordPress sites with the Softaculous PageLayer pagelayer plugin installed at affected versions through 1.9.4. Sites without this plugin are not indicated as affected by the provided sources.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. Exploitation requires low privileges and user interaction, which lowers urgency compared with unauthenticated server-side flaws but still matters for public WordPress estates.
Researcher notes
Evidence is limited to CVE metadata and Patchstack reference data. The affected-version narrative says through <=1.9.4, while the structured affected entry is sparse. No source in the bundle identifies a fixed version, proof of exploitation, or detailed exploit preconditions beyond the CVSS vector.
Mitigation direction
Check Softaculous and Patchstack guidance for a fixed PageLayer release.
Update PageLayer when a vendor-supported fixed version is available.
Disable or remove PageLayer where it is not business-required.
Restrict WordPress accounts that can use PageLayer functionality.
Require MFA and least-privilege roles for WordPress users.
Validation and detection
Inventory WordPress sites for the PageLayer pagelayer plugin.
Confirm installed PageLayer versions and flag through 1.9.4.
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.