CVE-2026-0575
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 · uneditedA security vulnerability has been detected in code-projects Online Product Reservation System 1.0. This impacts an unknown function of the file /handgunner-administrator/adminlogin.php of the component Administrator Login. Such manipulation of the argument emailadd/pass leads to sql injection. The attack may be performed from remote. The exploit has been disclosed publicly 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 confidenceSQL injection vulnerability in the administrator login function of code-projects Online Product Reservation System 1.0. The emailadd and pass parameters in /handgunner-administrator/adminlogin.php are not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands and potentially bypass authentication or exfiltrate data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the vulnerable login fileSearch for the file /handgunner-administrator/adminlogin.php in your web root directoryAffected if The file exists and is accessible via the web server
-
Verify product versionCheck the installed version of the Fabian Online Product Reservation System (or code-projects Online Product Reservation System) - typically found in README files, version info in source code, or the product's about pageAffected if The installed version is 1.0
-
Inspect the login code for SQL injection vulnerabilityOpen adminlogin.php and examine the code handling the emailadd and pass parameters - look for direct string concatenation in SQL queries without using prepared statements or parameter bindingAffected if The code uses unparameterized SQL queries with user input from emailadd and pass parameters
-
Check if the admin login endpoint is exposedAttempt to access the admin login page via HTTP/HTTPS to confirm the endpoint is active (e.g., visit the URL corresponding to /handgunner-administrator/adminlogin.php)Affected if The adminlogin.php page is reachable and accepts emailadd and pass parameters via GET or POST
You are affected if the Online Product Reservation System version 1.0 is installed, the adminlogin.php file exists with the vulnerable code path, and the login function accepts user input without parameterized queries.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement prepared statements/parameterized queries for all database operations in the login functionality. Additionally, apply input validation and output encoding. Consider deploying a WAF as a temporary compensating control while the code fix is being developed.
- Consultation6.0 h
- Implementation12.0 h
- Testing4.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,064.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0575 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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