/

CVE-2026-90846

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in PHPGurukul Expense Tracker

CVE-2026-90846

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized database access and data manipulation

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity SQL injection vulnerability in the PHPGurukul Daily Expense Tracker System 1.1 affects the password-recovery functionality. A remote attacker who can submit crafted values through the email or contact-number parameters may influence database queries and access or alter data.

Affected context

The vulnerability occurs in the /dets/forgot-password.php endpoint of PHPGurukul Daily Expense Tracker System 1.1 when request parameters used by the password-recovery workflow are incorporated into database operations without sufficient query separation or validation. Risk depends on the endpoint being reachable and on the application's database account having meaningful privileges.

Exploit preconditions

  • Attack surface: The remotely accessible password-recovery endpoint
  • Required access: Ability to send requests to the application; prior authentication may not be required
  • Trigger point: Processing of the email or contactno request parameters
  • Why exploitation is possible: User-controlled input may affect SQL query structure rather than being treated solely as data

Why this happens

The underlying bug is an injection flaw in which externally supplied values are combined with SQL statements without reliable parameter binding or equivalent query separation. This behavior maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command, with CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component describing the broader injection class. The insecure pattern allows input intended as a data value to influence database command interpretation.

Potential impact

  • An attacker may read data that should remain confidential
  • An attacker could modify or delete application records
  • Database queries may expose account or password-recovery information
  • The vulnerability may contribute to authentication or account-impacting attacks
  • A compromised database account could increase the impact across connected application components

General mitigation guidance

Mitigation generally focuses on ensuring that user-controlled values cannot

alter SQL command structure.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for every database operation
  • Apply allowlist-based validation appropriate to email and contact-number fields
  • Avoid constructing SQL statements through string concatenation
  • Return generic password-recovery responses that do not disclose record existence
  • Restrict database accounts to the minimum permissions required by the application
  • Keep sensitive recovery workflows isolated from administrative database capabilities
  • Treat client-side validation as supplemental rather than a security boundary

How teams detect issues like this

Organizations can look for SQL injection risks through:

  • Static analysis rules identifying SQL string concatenation with request parameters
  • Code review checks for unparameterized database calls in authentication and recovery workflows
  • Dynamic application testing that observes abnormal database errors or response differences
  • Web application firewall policies for suspicious injection patterns, used as a layered control
  • Database monitoring for unexpected query shapes, privilege use, or access to unrelated tables
  • CI policies requiring parameterized query APIs and security review for externally reachable endpoints

Sources

SourceLink
github.comgithub.com/usernamevnq/CVEs/issues/8
phpgurukul.comphpgurukul.com/
vuldb.comvuldb.com/cve/CVE-2026-90846
vuldb.comvuldb.com/submit/925687
vuldb.comvuldb.com/vuln/403398
vuldb.comvuldb.com/vuln/403398/cti

Frequently asked

questions

Yes. The affected password-recovery endpoint is remotely reachable, and

exploitation may be possible through supplied email or contactno values.

The exact scope depends on deployment configuration and database permissions.

The description does not establish that authentication is required. Because

the affected functionality is a password-recovery workflow, exposure may

exist before login, but access controls and routing configuration should be

verified.

The safest pattern is to use parameterized queries or prepared statements,

validate inputs according to their expected formats, and ensure database

errors are not returned to users.

Enforce secure database-access patterns in code review and CI, use least

privilege for application database accounts, test externally reachable

endpoints, and monitor database activity for anomalous query behavior.

Find out what's already
exploitable in your codebase.