CVE-2018-25185
Published: 26 March 2026
Summary
CVE-2018-25185 is a high-severity SQL Injection (CWE-89) vulnerability in Wecodex Restaurant Cms. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 36.9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).
Deeper analysis
CVE-2018-25185 is an SQL injection vulnerability (CWE-89) in Wecodex Restaurant CMS 1.0. The flaw resides in the login endpoint, where attackers can inject SQL code through the username parameter to manipulate database queries. It carries a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N), indicating high confidentiality impact with low integrity impact and no availability impact. The vulnerability was published on 2026-03-26.
Unauthenticated remote attackers can exploit this vulnerability by sending POST requests to the login endpoint containing malicious SQL payloads. Exploitation relies on boolean-based blind or time-based blind SQL injection techniques, enabling the extraction of sensitive database information without requiring prior authentication or user interaction.
Advisories and exploit details are documented in references including Exploit-DB (https://www.exploit-db.com/exploits/44730), VulnCheck (https://www.vulncheck.com/advisories/wecodex-restaurant-cms-sql-injection-via-login), and the vendor's product page (https://www.wecodex.com/item/view/restaurant-system-in-php-and-mysql/6). No specific patches or mitigation steps are detailed in the CVE description.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2018-21657
Vulnerability details
Wecodex Restaurant CMS 1.0 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the username parameter. Attackers can send POST requests to the login endpoint with malicious SQL payloads using boolean-based…
more
blind or time-based blind techniques to extract sensitive database information.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
SQL injection in unauthenticated public-facing login endpoint directly enables exploitation of public-facing applications (T1190) and extraction of sensitive data from databases via blind techniques (T1213.006).
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SI-10 directly prevents SQL injection by requiring validation of untrusted inputs like the username parameter in login requests.
SI-2 mandates timely identification, reporting, and correction of flaws such as this SQL injection vulnerability in the login endpoint.
SI-4 enables monitoring of the system to detect SQL injection attacks through anomalous login requests or query patterns.