CVE-2023-1893 json
Login Configurator <= 2.1 - Reflected Cross-Site Scripting
published 2023-07-17 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-24082
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The Login Configurator WordPress plugin through 2.1 does not properly escape a URL parameter before outputting it to the page, leading to a reflected cross-site scripting vulnerability targeting site administrators.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Login Configurator <=2.1 - Cross-Site Scripting nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/dbe6cf09-971f-42e9-b744-9339454168c7 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/173723/WordPress-Login-Configurator-2.1-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Unknown Login Configurator
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpscan.com
/vulnerability/dbe6cf09-971f-42e9-b744-9339454168c7
exploit, vdb-entry, technical-description, third-party-advisory
-
packetstormsecurity.com
/files/173723/WordPress-Login-Configurator-2.1-Cross-Site-Scripting.html
exploit, third-party-advisory
Sources
- CVE List CVE-2023-1893
- NVD CVE-2023-1893
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.