CVE-2025-25349: SQL Injection
Published Feb 12, 2025
·Updated
PHPGurukul Daily Expense Tracker System v1.1 is vulnerable to SQL Injection in /dets/add-expense.php via the costitem parameter.
Affected Software
2 affected components
Phpgurukul Daily Expense Tracker System=1.1
Phpgurukul Daily Expense Tracker System
Event History
Feb 12, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-25349?
CVE-2025-25349 is classified as a high severity vulnerability due to the risk of unauthorized access to the database.
2
How do I fix CVE-2025-25349?
To fix CVE-2025-25349, sanitize user inputs and use prepared statements or parameterized queries in the /dets/add-expense.php file.
3
What is the impact of CVE-2025-25349 on the affected software?
The impact of CVE-2025-25349 allows attackers to execute arbitrary SQL commands through the costitem parameter, potentially revealing sensitive information.
4
Which versions of the Daily Expense Tracker System are affected by CVE-2025-25349?
Only version 1.1 of the PHPGurukul Daily Expense Tracker System is affected by CVE-2025-25349.
5
Is CVE-2025-25349 being actively exploited?
There is currently no public information indicating that CVE-2025-25349 is being actively exploited in the wild.