dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4625

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 flaw has been found in SourceCodester Online Admission System 1.0. This affects an unknown function of the file /programmes.php. Executing a manipulation of the argument program can lead to sql injection. The attack can be launched remotely. The exploit has been published 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 Admission System 1.0 allows remote attackers to inject malicious SQL queries via the 'program' parameter in /programmes.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in programmes.php and similar files. Additionally, implement input validation and consider deploying a WAF as a defense-in-depth measure.

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 Admission System is installed
    Search your web server for files or directories containing 'online admission' or 'admission system' in the name. Check common web root locations like /var/www/html, /www, or C:\inetpub\wwwroot for an application folder named 'online admission system' or similar.
    Affected if The application is present on the system
  2. Verify the application version is 1.0
    Check for a version file, README, or any file containing 'version' or '1.0' within the application directory. Also check the footer or about page of the web application if accessible.
    Affected if The installed version is 1.0 (as stated in the affected products)
  3. Locate programmes.php in the web root
    Search for a file named 'programmes.php' within the application directory structure. This file should exist in the web-accessible portion of the application.
    Affected if programmes.php file exists in the application root
  4. Inspect programmes.php for the 'program' parameter handling
    Open programmes.php and search for occurrences of 'program' as a request parameter (look for $_GET['program'], $_POST['program'], or Request::get('program')). Check how this parameter is used in database queries.
    Affected if The code directly uses the 'program' parameter in SQL queries without proper escaping or prepared statements
  5. Check for proper input sanitization or parameterized queries
    Review the programmes.php code around the 'program' parameter usage. Look for functions like htmlspecialchars(), mysqli_real_escape_string, or parameter binding with prepared statements. Also check if any validation function is applied to the 'program' parameter before using it in SQL.
    Affected if No sanitization or parameterized queries are found for the 'program' parameter before database operations

If SourceCodester Online Admission System version 1.0 is installed with a programmes.php file that uses the 'program' parameter directly in SQL queries without sanitization or prepared statements, the environment is affected by CVE-2026-4625.

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 prepared statements/parameterized queries in programmes.php and similar files. Additionally, implement input validation and consider deploying a WAF as a defense-in-depth measure.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4625 — 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-4625 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