Security readout for executives and security teams
Plain-English summary
CVE-2024-51634 affects the WordPress Webriti Custom Login plugin through version 0.3. The issue is described as CSRF leading to reflected XSS, meaning a user could be tricked into a browser action that runs attacker-controlled script in site context.
Executive priority
Treat as a high-priority WordPress plugin exposure if the plugin is present. Prioritize inventory first, then removal, disablement, or vendor-guided update because the provided sources do not name a fixed version.
Technical view
The CVE describes CWE-352 in the webriti-custom-login-page package, with reflected XSS impact. CVSS 3.1 is 7.1: network reachable, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites running Webriti Custom Login version 0.3 or earlier. The source bundle does not provide CPEs, installation counts, or hosting-specific details.
Exploitation context
The record is not listed as CISA KEV, and the provided sources do not establish active exploitation. User interaction is required, so risk is highest where administrators or trusted users can be targeted.
Researcher notes
Evidence is concise: CVE and Patchstack identify CSRF to reflected XSS through version 0.3. Validate affected state without weaponized testing, and avoid assuming exploit maturity or a fixed release unless vendor guidance confirms it.
Mitigation direction
Inventory WordPress sites for webriti-custom-login-page and confirm installed version.
If version is 0.3 or earlier, review current vendor or Patchstack guidance.
Disable or remove the plugin where it is not business-critical.
Apply any vendor-provided fixed release when confirmed by trusted guidance.
Limit administrator exposure to unsolicited links until resolved.
Validation and detection
Check WordPress plugin inventory for Webriti Custom Login.
Confirm whether the installed version is 0.3 or earlier.
Review security tooling for CVE-2024-51634 or Patchstack detection coverage.
Inspect recent admin-user security alerts for unusual browser-driven activity.
Document whether the plugin is enabled, inactive, or removed.
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-352: 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.