Security readout for executives and security teams
Plain-English summary
CVE-2026-1503 affects the WordPress login_register plugin through version 1.2.0. If an attacker tricks an administrator into clicking a crafted link, the plugin can save malicious script into site settings. That script may run for users who view the affected page. Business risk is site integrity and visitor trust, not server takeover based on the cited CVSS.
Executive priority
Treat as a moderate-priority website integrity issue. Prioritize sites with public traffic, high brand sensitivity, or many administrators. If the plugin is present and no vendor fix is available, temporary removal or disablement is a reasonable risk-reduction decision.
Technical view
The issue combines CSRF on the settings page with insufficient sanitization and escaping of the login_register_login_post parameter. Wordfence rates it CVSS 3.1 4.3. The attacker needs administrator interaction, but no authentication. Scope is unchanged, with low integrity impact and no stated confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress sites running login_register versions up to and including 1.2.0. The source bundle does not identify affected installations, a patched version, or broader product impact.
Exploitation context
The sources describe a user-interaction attack: an unauthenticated attacker must trick an administrator into performing an action such as clicking a link. The CVE is not listed as KEV, and the provided sources do not state active exploitation.
Researcher notes
Evidence points to missing nonce validation and weak sanitization/escaping around login_register_login_post in login_register_admin.php. Public references include Wordfence and WordPress Trac code locations. No exploit code, fixed version, or active exploitation evidence is provided in the source bundle.
Mitigation direction
- Inventory WordPress sites for the login_register plugin and version.
- If version is 1.2.0 or older, check vendor guidance for an update or fix.
- Consider disabling or removing the plugin until vendor remediation is confirmed.
- Limit administrator browsing from logged-in WordPress sessions where practical.
- Review affected settings for unexpected script content.
Validation and detection
- Confirm whether login_register is installed on each WordPress site.
- Record the installed plugin version and compare against 1.2.0.
- Review plugin settings for unexpected HTML or script entries.
- Check whether vendor documentation names a fixed release.
- Monitor WordPress security sources for updated remediation guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2026-1503 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.