CVE-2026-5649
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 vulnerability has been found in code-projects Online Application System for Admission 1.0. This issue affects some unknown processing of the file /enrollment/admsnform.php of the component Endpoint. Such manipulation leads to sql injection. The attack can be executed remotely. The exploit has been disclosed to the 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 confidenceSQL injection vulnerability in the Online Application System for Admission 1.0 at endpoint /enrollment/admsnform.php. The vulnerability allows remote attackers to manipulate SQL queries through unsanitized input, potentially enabling data exfiltration or unauthorized database access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the application installationSearch the web root for the enrollment directory and admsnform.php file, or check if the application is accessible at /enrollment/admsnform.phpAffected if The Online Application System for Admission is present and the /enrollment/admsnform.php endpoint exists and responds to requests
-
Identify the application versionCheck any version file in the application root, examine the admin panel for version info, or look for a README/install file that states the versionAffected if The installed version is 1.0 of the Online Application System for Admission
-
Verify the enrollment form is activeAccess /enrollment/admsnform.php in a browser and submit a test enrollment form to confirm the endpoint processes user inputAffected if The enrollment form is functional and accepts user-submitted data that reaches the database
-
Confirm database interaction existsExamine the admsnform.php source code to verify it contains SQL queries that incorporate user input directly into query strings without visible sanitization or prepared statementsAffected if The code shows direct string concatenation of user input into SQL queries (look for $_POST or $_GET variables used in SELECT/INSERT/UPDATE statements without parameterization)
-
Check for input validation layerReview the application for any input validation, sanitization functions, or web application firewall configuration that may be mitigating the vulnerabilityAffected if No input sanitization or parameterized queries are implemented and there is no protective layer between user input and the SQL query construction
The environment is affected if the Online Application System for Admission version 1.0 is installed, the /enrollment/admsnform.php endpoint is accessible, and the code directly uses user input in SQL queries without sanitization or prepared statements.
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 dataRemediate by implementing parameterized queries or prepared statements for all database interactions in the affected file, adding input validation/sanitization, and applying the principle of least privilege to database accounts.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5649 — 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-5649 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