Quick answers
- Is CVE-2026-90844 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90844 being exploited in the wild.
- How severe is CVE-2026-90844?
- High severity, with a CVSS score of 7.3, published 15 September 2026.
- Which products and versions are affected?
- Phpgurukul Daily Expense Tracker System 1.1.
- Is there a fix for CVE-2026-90844?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-90844 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-90844?
- Check whether you run Phpgurukul Daily Expense Tracker System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a classic unauthenticated SQL injection (CWE-89) in the login component (/dets/index.php). The email parameter from the POST request is concatenated directly into a SQL query without sanitization or parameterized statements, while the password is hashed with MD5 before insertion. An attacker can inject SQL operators in the email field—such as `' OR '1'='1' LIMIT 1-- -`—to bypass authentication and login as the first user in the database or any known user. No server-side validation, escaping, or prepared statements are implemented. Network access is required and no authentication is needed to exploit this vulnerability. Remediation requires use of prepared statements with parameter binding and server-side input validation.
Affected products
- PHPGurukul Daily Expense Tracker System 1.1
Timeline
- 2026-08-12: disclosed: Vulnerability reported on GitHub
- 2026-09-15: advisory: Published as CVE-2026-90844 in NVD