Library Management System CVE-2026-78200

Exploitation requires a valid low-privilege authenticated session on the Library Management System 1.0 web application (CVSS PR:L). The vulnerable code path is within editbooks.php, meaning the attacker must have access to the book editing functionality. The attack is network-accessible (AV:N) with no additional complexity or user interaction required beyond authentication. Exploitation is limited by the authentication requirement - unauthenticated remote exploitation is not supported by the available CVSS vector. No specific non-default configuration is required; any standard deployment of version 1.0 with authenticated user access to editbooks.php is vulnerable.

The CVSS 4.0 base score of 2.1 (AV:N/AC:L/AT:N/PR:L/UI:N) reflects low confidentiality, integrity, and availability impact, and requires low-privilege authentication - contextualizing this as a moderate-severity issue rather than critical. No KEV listing exists, meaning active exploitation has not been confirmed by CISA. However, a public proof-of-concept is available via GitHub, which meaningfully lowers the bar for opportunistic attackers and is the most significant escalating risk signal here. EPSS data was not provided in the intelligence feed; given the niche nature of the product, widespread automated scanning is plausible but not confirmed. The overall real-world priority is moderate: the authenticated requirement and limited CVSS impact constrain blast radius, but the POC availability means any internet-exposed instance with authenticated users should be treated as urgently patchable.

An attacker with a low-privilege account on the Library Management System navigates to editbooks.php and submits a crafted value in the ID parameter containing SQL metacharacters (e.g., a UNION-based or boolean-blind injection payload). The unsanitized input is interpolated into the SQL query, allowing the attacker to extract database contents, enumerate user credentials, or modify book records. A public proof-of-concept exists on GitHub, meaning this scenario can be replicated by a minimally skilled attacker with access to the application.