dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4624

HIGH · 7.3 CVSS v3.1 Published 2026-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was detected in SourceCodester Online Library Management System 1.0. The impacted element is an unknown function of the file /home.php of the component Parameter Handler. Performing a manipulation of the argument searchField results in sql injection. The attack can be initiated remotely. The exploit is now public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in SourceCodester Online Library Management System 1.0 allows remote attackers to inject malicious SQL queries via the searchField parameter in /home.php. The application fails to properly sanitize user input before using it in database queries.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for the searchField parameter in /home.php. Validate and sanitize all user inputs before using them in database operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SourceCodester Online Library Management System is installed
    Search the web root directory for files indicating this application, such as check_login.php, class.php, or other PHP files containing the application name
    Affected if The application files are found on the server
  2. Verify the application version is 1.0
    Check any version file, README, or footer in the application for the version number
    Affected if The installed version is 1.0
  3. Locate the vulnerable /home.php file
    Find home.php in the web directory, typically in the document root or a subdirectory
    Affected if The file /home.php exists in the application installation
  4. Inspect the searchField parameter handling in /home.php
    Open /home.php and search for 'searchField' to see how the parameter is used in database queries - look for direct concatenation into SQL strings without escaping or prepared statements
    Affected if The searchField parameter is directly concatenated into SQL queries without parameterized queries or input sanitization
  5. Test for SQL injection manually (optional)
    Send a crafted request to the endpoint using searchField with a SQL injection payload such as ' OR '1'='1 and observe the response
    Affected if The application returns unexpected database results or errors indicating SQL injection is possible

A user is affected if they have SourceCodester Online Library Management System version 1.0 installed with the /home.php file present and the searchField parameter vulnerable to SQL injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) for the searchField parameter in /home.php. Validate and sanitize all user inputs before using them in database operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4624 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data