Safeguard
Vulnerability Analysis•

CVE-2025-14668: High SQL Injection in Online Examination System

CVE-2025-14668 is a SQL injection in Campcodes Online Examination System with no listed fix. Restrict access and switch the query to prepared statements.

Safeguard Security Team
4 min read

CVE-2025-14668 is a high severity SQL injection flaw (CVSS 7.3) in Campcodes Advanced Online Examination System 1.0. The the Username argument handled by /query/loginExe.php is used in a database query without safe handling. The record lists no fixed version, so restrict access now and rewrite the query with prepared statements.

What's affected

The record names Campcodes Advanced Online Examination System 1.0. The vulnerable file is /query/loginExe.php, and the argument involved is the Username argument.

Here is what the record and its scoring say:

  • Severity: High, CVSS 7.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L.
  • Network reachable, low complexity, no privileges and no user interaction required, according to that vector.
  • Impact is scored as low for each of confidentiality, integrity and availability.
  • Fixed version: none listed in the record.
  • Exploitation in the wild: the record is not in the CISA KEV catalog. It does say exploit details have been made public.

A public write up exists on GitHub and is linked from the record. This post does not reproduce its test details.

How to check if you're exposed

This is application code, not a package you install from a registry, so start with a file search on the server or in your repositories.

# Is the application present?
grep -ril "loginExe.php" /var/www 2>/dev/null

# Does your web server log show traffic to the page?
grep "loginExe.php" /var/log/nginx/access.log | tail -n 50

Then open loginExe.php and find where Username is read. If its value is joined into an SQL string, you have the flaw described here. If it is passed to a prepared statement as a bound value, that path is not affected by this class of bug.

Also look at the log lines for unusual characters or very long values in the query string. Odd entries are a prompt to investigate, not proof of compromise.

If the application lives in a repository you track, the free in-browser dependency scan will list known CVEs for the packages it can identify. A hand copied PHP project often has no manifest at all, so an inventory by hand is still needed.

What to do now

  1. Find every copy of the application, including test and staging servers.
  2. Take it off the public internet, or put it behind a VPN or an IP allow list, until the code is fixed.
  3. Check the vendor site for a patched release. The record lists none, so do not assume one exists.
  4. Rewrite the query in loginExe.php so values are bound as parameters, never joined into the SQL text.
  5. Give the application's database account only the rights it needs. It should not own the schema or read unrelated tables.
  6. Review web server and database logs for the period since the public disclosure date of 2025-12-14.
  7. If the application is not essential, retire it. Unmaintained code is a standing risk.

A prepared statement keeps the SQL text and the data apart. This pattern with PDO is the usual fix:

$stmt = $pdo->prepare('SELECT * FROM items WHERE id = :id');
$stmt->execute(['id' => $id]);

Why it matters

SQL injection is the case where an application builds a database command from text it did not control. CWE-89 describes exactly that: special elements in input are not neutralized before the query is built. The parent class, CWE-74, covers injection into any downstream component. Once input can change the shape of a query, the database stops being limited to what the developer meant to ask.

Public disclosure does not equal confirmed exploitation. This CVE is not in the CISA KEV catalog. But when exploit details are public, scanners and curious visitors can find an exposed copy quickly, so the gap between disclosure and abuse can be short.

Small business applications of this kind are often installed once and then forgotten. That is the real risk: nobody owns the update, and no vendor patch may ever arrive.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Is there a patched version of Advanced Online Examination System?

The CVE record lists no fixed version and the references I could see are not a vendor patch. Check Campcodes's site, and do not rely on a release number alone. Fixing the query in your own copy is the dependable route.

Does a login protect this page?

Do not count on it. The CVSS vector scores no privileges required, and that is the scoring the record carries. Test your own deployment before you trust any access control in front of it.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.