CVE-2026-1503 json
login_register <= 1.2.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting
published 2026-03-21 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-14181
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
The login_register plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting in all versions up to, and including, 1.2.0. This is due to missing nonce validation on the settings page and insufficient input sanitization and output escaping on the 'login_register_login_post' parameter. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via a forged request granted they can trick an administrator into performing an action such as clicking on a link.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected products
- frankkoenen Plugin Name: login_register
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/8c82d209-3c69-4d6e-a129-d519f6601540?source=cve
- plugins.trac.wordpress.org /browser/login-register/tags/1.2.0/login_register_admin.php#L12
- plugins.trac.wordpress.org /browser/login-register/tags/1.2.0/login_register_admin.php#L14
- plugins.trac.wordpress.org /browser/login-register/tags/1.2.0/login_register_admin.php#L69
Sources
- CVE List CVE-2026-1503
- NVD CVE-2026-1503
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.