Unauthenticated SQL injection via unsanitized fname parameter
Published May 16, 2025 · Updated May 16, 2025
SQL injection in PHPGurukul Beauty Parlour Management System 1.1 allows remote attackers to manipulate the database through fname. The contact.php handler inserts the POST fname value directly into a SQL query without sanitization, validation, or parameter binding. No login is required; a crafted request can read, modify, or delete database records and delay database responses with a time-based payload.
Summary
What happened
SQL injection in PHPGurukul Beauty Parlour Management System 1.1 allows remote attackers to manipulate the database through fname. The contact.php handler inserts the POST fname value directly into a SQL query without sanitization, validation, or parameter binding. No login is required; a crafted request can read, modify, or delete database records and delay database responses with a time-based payload.
The record
- CVE
- CVE-2025-4758
- Published
- May 16, 2025
- Updated
- May 16, 2025
- Vendor
- PHPGurukul
- Product
- Beauty Parlour Management System
- Classifications
- CWE-74, CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 2025CVE publishedPublication date reported by the CVE source.
- May 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- contact.php fname time-based blind SQL injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo