Quick answers
- Is CVE-2026-90845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90845 being exploited in the wild.
- How severe is CVE-2026-90845?
- Low severity, with a CVSS score of 3.5, published 15 September 2026.
- Which products and versions are affected?
- Phpgurukul Daily Expense Tracker System 1.1.
- Is there a fix for CVE-2026-90845?
- 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-90845 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-90845?
- 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
This is a stored cross-site scripting (CWE-79) vulnerability in which user-supplied data (full name, expense items, costs, and profile fields) is rendered directly into HTML using raw PHP echo statements without output encoding. The vulnerable component is present across multiple pages including sidebar.php, manage-expense.php, and several report-detailed pages. Exploitation requires authentication but no additional user interaction beyond the attacker injecting a payload (via the expense form or profile update). An authenticated attacker can inject JavaScript that persists in the database and executes in the browsers of all other users who view the affected pages, particularly the sidebar which is loaded on every authenticated page. No patch information is currently available.
Affected products
- PHPGurukul Daily Expense Tracker System 1.1
Timeline
- 2026-08-12: disclosed: Vulnerability reported on GitHub
- 2026-09-15: advisory