PHPGurukul Men Salon Management System 2.0 contains an SQL injection vulnerability in the handling of the email parameter in the index.php component. A remote attacker can submit malicious SQL input through this parameter, reportedly enabling arbitrary code execution and access to sensitive information.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository documents a proof-of-concept (PoC) exploit for CVE-2024-30998, a SQL injection vulnerability in PHPGurukul Men Salon Management System version 2.0. The vulnerability exists in the 'email' parameter of the index.php file, which fails to properly sanitize user input. The PoC demonstrates exploitation using sqlmap, with example payloads for both boolean-based and time-based blind SQL injection. The repository contains two markdown files: one with detailed vulnerability and exploitation information, and a README summarizing the issue and mitigation advice. No executable code is present; the repository serves as documentation and a guide for exploiting the vulnerability. The main attack vector is network-based, targeting the web application's HTTP interface. The endpoints identified include the application's URL (e.g., http://localhost/msms), the vulnerable index.php script, and the backend database (msmsdb).
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.