Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site with vulnerable plugin
-
DeliverySend crafted request with SQL payload
-
ExploitInjection executes in database query
-
ExecutionEnumerate schema and dump wp_users
-
ImpactExfiltrate password hashes and user data
Vulnerability Assessment
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation (AV:N/AC:L/PR:N/UI:N) against default installations of the Library Management System WordPress plugin at any 3.5.x version below 3.5.8. The concrete prerequisite is simply that a vulnerable version of the plugin is installed and its injectable request parameter is reachable over the network; no configuration toggle, feature enablement, or login is required. The main limiting factor is deployment scope: only WordPress sites that have this specific (relatively niche) plugin installed and not yet updated to 3.5.8 are exploitable. |
| Impact | Signals are mixed but lean toward real, opportunistic risk. The CVSS vector (AV:N/AC:L/PR:N/UI:N, C:H, S:C) describes a network-reachable, low-complexity, unauthenticated attack with high confidentiality impact and a scope change, yielding 8.6 (High). SSVC reinforces this: exploitation is at POC stage, the attack is Automatable=yes, and Technical Impact is partial (confidentiality-only, no integrity/availability). Countering that, EPSS is low at 0.18% (7th percentile) and the CVE is NOT in CISA KEV, so there is no evidence of active mass exploitation yet. The practical read: a straightforward, scriptable SQLi with public POC that is well within reach of automated WordPress scanners, but current observed exploitation is limited - treat as a prompt-patch item rather than an emergency, while noting that the automatable + unauthenticated combination means opportunistic scanning could raise EPSS quickly. |
| Exploit ScenarioDerived | An attacker finds a WordPress site running Library Management System < 3.5.8 and sends a crafted HTTP request that injects SQL into the vulnerable parameter, requiring no authentication or user interaction. Using the publicly available exploit technique, they enumerate the database and dump the wp_users table, harvesting usernames, emails, and password hashes for offline cracking or credential reuse. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
SQL injection in the Library Management System WordPress plugin before 3.5.8 lets unauthenticated attackers inject arbitrary SQL through an unsanitized request parameter and read data straight from the WordPress database, including user password hashes. Publicly available exploit code exists and the flaw was reported by WPScan, though the EPSS probability is low (0.18%, 7th percentile) and it is not on CISA KEV. The vendor has shipped a fixed release (3.5.8), making patching the clear priority for affected sites.
RemediationAI
Vendor-released patch: version 3.5.8 - upgrade the Library Management System plugin to 3.5.8 or later, which is the definitive fix. Until the update is applied, restrict exposure by placing a WAF/virtual-patch rule in front of WordPress to block SQL-injection patterns on the plugin's request parameters (trade-off: rule tuning may cause false positives and is not a substitute for the patch), or temporarily deactivate the plugin if library functionality is non-critical (trade-off: removes the feature entirely). Because password hashes may already have been exposed on internet-facing sites, force a password reset for all WordPress users and rotate secrets after patching. See the WPScan advisory (https://wpscan.com/vulnerability/762dd8c3-8972-46ef-90c2-9f3f5dce4370/) for details.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is a third-party WordPress plugin (CPE cpe:2.3:a:unknown:library_management_system) that adds library catalog/loan management functionality to WordPress sites. The root cause is a classic SQL injection (CWE-89, though the input lists CWE as N/A): a user-supplied parameter is concatenated into a SQL statement without sanitization or escaping/parameterization. Because WordPress plugins run queries against the shared site database via the global $wpdb layer, one injectable query exposes not just plugin tables but the entire schema - notably wp_users, where password hashes and emails are stored.
Know when Library Management System gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Unauthenticated network SQLi with low complexity (AV:N/AC:L/PR:N/UI:N) reads the full DB across a security-authority boundary (S:C, C:H) with no write or availability impact (I:N/A:N).
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Library Management System WordPress plugin before 3.5.8 does not sanitize and escape a user-supplied parameter before using it in a SQL statement, allowing unauthenticated attackers to perform SQL injection and extract arbitrary data from the database, including user password hashes.
Articles & Coverage 1
Executive ViewAI
The Library Management System WordPress plugin before version 3.5.8 contains a vulnerability enabling unauthenticated attackers to access sensitive data and user credentials directly from affected WordPress databases. With public exploit code available and a CVSS score of 8.6, this represents an immediate threat to data security and user account integrity across any organization using the affected plugin versions.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Library Management System
View allA vulnerability, which was classified as critical, was found in code-projects Library Management System 2.0. Rated criti
In Library Management System 1.0 the /card/in-card.php file id_no parameters are vulnerable to SQL injection. Rated crit
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the bookId parameter at /admi
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the RollNo parameter at /admi
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the M_Id parameter at /admin/
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /libraria
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the RollNo parameter at /libr
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the bookId parameter at /libr
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the Section parameter at /sta
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the Section parameter at /lib
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /staff/st
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /staff/bo
EUVD-2026-43293
GHSA-qvmr-hx75-cf7j
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB