CVE-2023-5203
SQLi in Swit Wp Sessions Time Monitoring Full Automatic ≤ 1.0.9
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-5203 is a high-severity SQL Injection (CWE-89) vulnerability in Swit Wp Sessions Time Monitoring Full Automatic. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The WP Sessions Time Monitoring Full Automatic WordPress plugin before version 1.0.9 contains an SQL injection vulnerability (CWE-89) because it fails to sanitize incoming request URLs and query parameters before incorporating them into database queries. The flaw affects any site running the plugin and carries a CVSS 3.1 score of 7.5, reflecting network-exploitable impact limited to confidentiality.
Unauthenticated remote attackers can leverage blind time-based SQL injection techniques, and in some configurations error-based or union-based methods, to extract arbitrary data from the WordPress database without requiring credentials or user interaction.
Public references on WPScan document the issue and point to the availability of version 1.0.9, which addresses the lack of input sanitization. The associated EPSS score has reached a peak of 0.4338, indicating sustained exploitation interest following disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57534
Vulnerability Data
The WP Sessions Time Monitoring Full Automatic WordPress plugin before 1.0.9 does not sanitize the request URL or query parameters before using them in an SQL query, allowing unauthenticated attackers to extract sensitive data from the database via blind time…
more
based SQL injection techniques, or in some cases an error/union based technique.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.5
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.6 only improves knowledge flow, awareness of threats/patches and access to specialist advice; it does not stop SQL injection from being exploitable in code that still contains the flaw.