CVE Intelligence
Analysis AI-assisted

CVE-2026-1688: itsourcecode Directory Management System SQL Injection

CVE-2026-1688 is an SQL injection flaw (CWE-89) in the Username argument of /admin/index.php in itsourcecode Directory Management System 1.0, which can be triggered remotely. NVD scores it CVSS 3.1 9.8 (Critical). The record notes a public exploit disclosure but no CISA KEV listing, and no vendor fix is identified.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

CVE-2026-1688 is an SQL injection issue (CWE-89) affecting itsourcecode Directory Management System 1.0. According to the record, the flaw involves an unspecified function in /admin/index.php and is triggered by manipulating the Username argument. The main sources consulted are the NVD entry and the VulDB/CNA entries listed in the references.

Impact

SQL injection can allow an attacker to interfere with the database queries an application runs. Depending on how the application uses its database, this could expose, alter or delete stored data, and could affect authentication logic. The NVD vector (C:H/I:H/A:H) indicates high confidentiality, integrity and availability impact as scored by NVD. The actual impact in a given deployment is an inference that depends on configuration and data.

Affected products and versions

  • The description names itsourcecode Directory Management System 1.0.
  • The structured affected-product field names Clive 21 Directory Management System, version 1.0.
  • These product names do not match. The record does not resolve which product name is correct, so administrators should verify their installed product and version against the vendor site and the advisories.
  • Scores from CNAs differ: VulDB lists 7.3 under CVSS 3.1, 5.5 under CVSS 4.0 and 7.5 under CVSS 2.0; NVD lists 9.8 under CVSS 3.1.

Exploitation status

  • The CISA KEV catalog does not list this CVE in the record, so no confirmed active exploitation is reported in the sources consulted.
  • The record states that an exploit has been disclosed publicly. A GitHub issue referenced by the record is tagged as an exploit reference. This is a public disclosure, not evidence of exploitation in the wild.
  • No EPSS score is available in the record.

Remediation and mitigation

  • The record contains no vendor patch or fixed version. The only listed fix is a mitigation reference to a GitHub issue. Treat the absence of a fixed version as unknown, not as proof that no fix exists.
  • Restrict access to administrative interfaces such as /admin/ to trusted networks and enforce strong authentication.
  • Check with itsourcecode for updates or guidance. If you maintain the code, use parameterized queries and validate input on authentication fields.
  • Consider web application firewall rules and monitoring as temporary compensating controls, and verify their effectiveness in a test environment.
  • If the application is exposed to the internet and cannot be secured, consider taking it offline until a remediation is confirmed.

Detection guidance

  • Review web server and application logs for unusual or malformed requests to /admin/index.php, especially requests where the Username parameter contains unexpected characters or repeated attempts.
  • Monitor database error messages surfaced by the application, which can indicate injection attempts.
  • Alert on successful logins to administrative accounts from unexpected sources or at unusual times.

Limitations of the available information

  • The record does not identify the vulnerable function name, the exact affected version range beyond version 1.0, or a vendor fix.
  • The product name conflict between the description and the affected-product field is unresolved.
  • No KEV, EPSS or SSVC data is available in the record.
  • The analysis relies on the record and listed references; the content of the referenced pages was not independently verified here.

Frequently asked questions

Is CVE-2026-1688 being actively exploited?

The record shows it is not listed in the CISA KEV catalog, so no confirmed active exploitation is reported in the sources consulted. The record does state that an exploit has been disclosed publicly.

Is there a fixed version available?

The record does not list a vendor fixed version. It only includes a mitigation reference to a GitHub issue, so the availability of a fix is unknown.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.