Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconRegister Subscriber account or use existing credentials
-
DeliveryIdentify vulnerable parameter in Library Management System plugin
-
ExploitCraft SQL injection payload using public POC
-
InstallSubmit malicious HTTP request to WordPress endpoint
-
C2Extract wp_users table including password hashes
-
ExecuteCrack hashes offline
-
ImpactAuthenticate as administrator or reuse credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid WordPress account with at minimum Subscriber-level privileges - the lowest authenticated role in a default WordPress installation. No special plugin configuration, non-default settings, or elevated permissions beyond a basic registered account are required. On sites with open user self-registration enabled (a common configuration), this is functionally equivalent to unauthenticated exploitation since any visitor can create a Subscriber account. Limiting factors: the target site must have the vulnerable plugin installed and active; the attacker must possess at least one valid WordPress session on the target site; sites that disable self-registration and restrict account creation to administrators reduce the attacker pool to trusted users only. The CVSS vector confirms AV:N (network-reachable), AC:L (no special conditions or race conditions), PR:L (low-privilege authentication required), and UI:N (no victim interaction needed). |
| Impact | The provided CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, score 4.3) contains a material scoring error: C:N (no confidentiality impact) is assigned despite the CVE description explicitly stating that attackers can extract 'arbitrary data from the database, including user password hashes' - a plainly high-confidentiality outcome. This discrepancy is flagged; the official score significantly understates real risk and should not be used as a sole triage signal. EPSS at 0.17% (6th percentile) suggests limited current automated or mass exploitation activity, but a publicly available POC confirmed by WPScan lowers the technical barrier to manual exploitation to near-zero. No CISA KEV listing means large-scale active exploitation is not confirmed at time of analysis, though absence from KEV does not indicate safety. The PR:L requirement (Subscriber role) limits the attacker pool to registered users, but on WordPress sites with open self-registration this is effectively equivalent to unauthenticated access. Password hash extraction is a high-value objective enabling offline credential cracking and subsequent account takeover across the site and potentially reused credentials elsewhere. |
| Exploit ScenarioDerived | An attacker registers a free Subscriber account on a target WordPress site running Library Management System before 3.6.7, or uses an existing low-privilege account. Using the publicly available POC from WPScan, the attacker submits a crafted HTTP request with a SQL injection payload in the vulnerable plugin parameter. The database returns the wp_users table contents, including hashed passwords for all WordPress users including administrators. The attacker then runs the hashes through an offline cracking tool to recover plaintext credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
SQL injection in the Library Management System WordPress plugin (all versions before 3.6.7) allows any user holding a Subscriber role or higher to inject arbitrary SQL into the underlying WordPress database, extracting sensitive records including user password hashes. A publicly available proof-of-concept exploit is confirmed via WPScan. No CISA KEV listing exists and EPSS sits at 0.17% (6th percentile), indicating limited observed automated exploitation, but the low privilege bar and public POC make this a meaningful and urgent patching priority for any affected site.
RemediationAI
Update the Library Management System WordPress plugin to version 3.6.7 or later immediately; this is the vendor-released patch confirmed available per the WPScan advisory at https://wpscan.com/vulnerability/7a9b3fff-f454-4764-ad60-0b273781f7b4/. Updates can be applied from the WordPress admin dashboard under Plugins > Updates or via WP-CLI with 'wp plugin update'. If patching cannot be performed immediately, deactivate the plugin entirely - this eliminates the attack surface but also removes all library management functionality. As an additional compensating control, disable WordPress user self-registration (Settings > General > uncheck 'Anyone can register') to prevent unauthenticated individuals from obtaining Subscriber accounts and exploiting this flaw; note this affects legitimate user onboarding workflows. Do not rely on WAF rules alone as the primary mitigation, since WAF bypass of SQLi payloads is well-documented. No exact patch commit or PR reference is available in the provided data beyond the version number.
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 product is the Library Management System plugin for WordPress, identified by CPE cpe:2.3:a:unknown:library_management_system:*:*:*:*:*:*:*:*. The root cause maps to CWE-89 (Improper Neutralization of Special Elements Used in an SQL Command): a user-controlled HTTP parameter is concatenated directly into a SQL query without sanitization or use of prepared statements or parameterized queries - a foundational web security failure. WordPress's Subscriber role is the lowest authenticated role available in a default WordPress installation, meaning any registered user qualifies as a potential attacker. The exposed database includes the wp_users table, which stores bcrypt or MD5-iterated password hashes for all WordPress accounts, making this an effective credential-harvesting vulnerability.
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:L/UI:N/S:U/C:N/I:L/A:N
C:H assigned independently because extraction of arbitrary database data including all user password hashes is a high confidentiality impact; the official C:N appears to be a scoring error.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Library Management System WordPress plugin before 3.6.7 does not sanitize and escape a user-supplied parameter before using it in a SQL statement, allowing users with a role as low as Subscriber to perform SQL injection and extract arbitrary data from the database, including user password hashes.
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-55029
GHSA-2c9h-p9wv-wmqh
NVD
CVE.org
EPSS
Exploit-DB