CVE Alert: CVE-2025-11662 – SourceCodester – Best Salon Management System

CVE-2025-11662

HIGHNo exploitation known

A security flaw has been discovered in SourceCodester Best Salon Management System 1.0. Impacted is an unknown function of the file /booking.php. The manipulation of the argument serv_id results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be exploited.

CVSS v3.1 (7.3)
Vendor
SourceCodester
Product
Best Salon Management System
Versions
1.0
CWE
CWE-89, SQL Injection
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Published
2025-10-13T05:02:07.389Z
Updated
2025-10-13T05:02:07.389Z

AI Summary Analysis

**Risk verdict**: High risk due to remote SQL injection with publicly disclosed exploit; active exposure is likely and warrants urgent attention.

**Why this matters**: An attacker can read or modify database content, exfiltrate sensitive records, or derail the application without user interaction. The remote, low-complexity nature raises the potential for automated scanning and mass exploitation across affected deployments.

**Most likely attack path**: Attackers can trigger the vulnerability by supplying crafted input to a web endpoint over the network, without authentication or user interaction. The CVSS metrics indicate remote, unauthenticated access with low attack complexity and minimal user involvement, enabling potential data disclosure or modification and possible subsequent lateral movement within the web/app tier.

**Who is most exposed**: Internet-facing installations of web-based management systems that trust user-supplied input in SQL queries, especially older 1.0 builds with insufficient parameterisation or input sanitisation, are at highest risk.

**Detection ideas**:

  • Web server logs show repeated requests to the vulnerable endpoint with suspicious serv_id payloads.
  • Database logs reveal abnormal queries or error messages indicating SQL injection patterns.
  • WAF alerts for SQLi signatures targeting the affected URI.
  • Unusual spikes in failed or delayed responses from the application layer.
  • IOCs: known exploit strings or payloads associated with the public release.

**Mitigation and prioritisation**:

  • Apply vendor-provided patch or upgrade to non-vulnerable version; implement parameterised queries and strict input validation.
  • Implement WAF rules to block SQLi attempts on the endpoint; enforce least-privilege DB access from the web tier.
  • Add comprehensive monitoring for the affected endpoint and enable alerting on anomalous query patterns.
  • Conduct a rapid impact assessment and run a targeted remediation window; coordinate change management for production environments.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.