CVE-2018-25425: Yot CMS 3.3.1 SQL Injection via aid and cid Parameters
Yot CMS 3.3.1 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the aid and cid parameters. Attackers can send GET requests to index.php with crafted SQL payloads in the aid or cid parameters to extract database information including table and column names.
Security readout for executives and security teams
Plain-English summary
Yot CMS 3.3.1 has an unauthenticated SQL injection issue in public request parameters. A remote attacker could read sensitive database information and may alter some data. The provided sources do not show confirmed active exploitation or a vendor patch.
Executive priority
Treat as high priority for any public Yot CMS 3.3.1 site because attackers need no account and may access sensitive database contents. Prioritize discovery, exposure reduction, and vendor guidance review.
Technical view
CVE-2018-25425 is CWE-89 in Yot CMS 3.3.1. The aid and cid parameters to index.php are reported as injectable, allowing arbitrary SQL queries and database metadata extraction. CVSS 4.0 is 8.8, with network access, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most likely where Yot CMS 3.3.1 is internet-accessible. The source bundle names only version 3.3.1 and provides no CPEs, so other versions should not be assumed affected without vendor or advisory evidence.
Exploitation context
A public ExploitDB reference exists, so practical exploitation information is available publicly. The source bundle marks KEV as false and provides no cited evidence of active exploitation in the wild.
Researcher notes
Evidence is limited to Yot CMS 3.3.1, aid and cid parameters, and database metadata extraction. Do not generalize to other versions. Public exploit availability increases operational risk, but active exploitation is not established by the provided sources.
Mitigation direction
Identify and prioritize any Yot CMS 3.3.1 deployments.
Check vendor guidance for a fixed release or official workaround.
Remove or isolate internet exposure if no supported fix is available.
Restrict access to affected CMS routes at the network or application layer.
Review database privileges used by the CMS and reduce unnecessary access.
Validation and detection
Inventory public sites and code repositories for Yot CMS 3.3.1.
Confirm deployed CMS version using safe administrative or package evidence.
Review access logs for suspicious index.php requests using aid or cid.
Check whether affected routes are reachable without authentication.
Verify CMS database credentials have least-privilege permissions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.