CVE-2018-25425
Yot CMS 3.3.1 SQL Injection via aid and cid Parameters
Publication date: 2026-05-30
Last updated on: 2026-05-30
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| yot_cms | yot_cms | to 3.3.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2018-25425 is an SQL injection vulnerability found in Yot CMS version 3.3.1. It allows unauthenticated attackers to inject malicious SQL code through the 'aid' and 'cid' parameters in GET requests to the index.php file.
By exploiting this flaw, attackers can execute arbitrary SQL queries, enabling them to extract sensitive database information such as table and column names.
How can this vulnerability impact me? :
This vulnerability can have a significant impact as it allows attackers to access sensitive database information without authentication.
Attackers can extract database schema details, which may lead to further exploitation such as data theft, unauthorized data manipulation, or gaining deeper access to the system.
The high severity score (CVSS 8.8) reflects the potential for serious confidentiality breaches.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by sending crafted GET requests to the affected Yot CMS instance targeting the 'aid' and 'cid' parameters in the index.php file.
For example, you can test the vulnerability by using curl commands to inject SQL payloads and observe the responses for database information leakage.
- curl "http://<target>/index.php?page=articles&op=art&aid=1' OR '1'='1"
- curl "http://<target>/index.php?page=articles&op=cat&cid=1' OR '1'='1"
If the response contains database errors or reveals table or column names, it indicates the presence of the SQL injection vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable parameters and applying input validation or sanitization to the 'aid' and 'cid' parameters in the index.php file.
If possible, update Yot CMS to a version that patches this vulnerability or apply available security patches.
Additionally, consider implementing a Web Application Firewall (WAF) to block malicious SQL injection attempts targeting these parameters.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in Yot CMS 3.3.1 allows attackers to extract sensitive database information, including table and column names, without authentication.
Such unauthorized access to sensitive data can lead to violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.
Therefore, exploitation of this vulnerability could compromise compliance with these standards by exposing confidential data.