Skip to main content
CVE-2025-5546VulnerabilityPublished

CVE-2025-5546: PHPGurukul Daily Expense Tracker System · SQL Injection

Affects PHPGurukul Daily Expense Tracker SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
PHPGurukul Daily Expense Tracker SystemAffected
  • =1.1
Fixed in–

AI-suggested

Organizations should immediately audit their use of PHPGurukul Daily Expense Tracker System 1.1 and restrict access to the /expense-reports-detailed.php endpoint. Implement input validation and parameterized queries or prepared statements to prevent SQL injection. If source code access is available, developers should sanitize and validate 'fromdate' and 'todate' parameters rigorously. Network-level controls such as web application firewalls (WAFs) should be configured to detect and block SQL injection attempts targeting these parameters. Monitoring and logging of database queries and application logs should be enhanced to detect anomalous activities. Until an official patch is released, consider isolating the application from external networks or limiting access to trusted IP addresses. Conduct penetration testing focused on SQL injection vectors to identify and remediate similar vulnerabilities. Finally, maintain an incident response plan to quickly address any exploitation attempts.

Description

A vulnerability classified as critical was found in PHPGurukul Daily Expense Tracker System 1.1. This vulnerability affects unknown code of the file /expense-reports-detailed.php. The manipulation of the argument fromdate/todate leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…