CVE-2025-8811
BaseFortify
Publication date: 2025-08-10
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| code-projects | simple_art_gallery | 1.0 |
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. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8811 is a critical SQL injection vulnerability in version 1.0 of the Simple Art Gallery software, specifically in the /Admin/registration.php file. It occurs because the application does not properly sanitize or validate the 'fname' parameter, allowing attackers to inject malicious SQL code. This improper handling enables attackers to manipulate SQL queries, potentially leading to unauthorized database access and modification. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely exploit the system without authentication. They can gain unauthorized access to the database, retrieve sensitive information, modify or delete data, take control of the system, and disrupt services. The vulnerability compromises the confidentiality, integrity, and availability of the affected system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by scanning for the presence of the vulnerable endpoint /Admin/registration.php and testing the 'fname' parameter for SQL injection. Attackers may use Google dorking with the query "inurl:Admin/registration.php" to identify vulnerable targets. To detect exploitation attempts or test the vulnerability, you can use tools like sqlmap or manual curl commands to inject SQL payloads into the 'fname' parameter. For example, a curl command to test might be: curl -G "http://target-site/Admin/registration.php" --data-urlencode "fname=' OR '1'='1". Monitoring web server logs for suspicious requests to /Admin/registration.php with unusual 'fname' parameter values can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replace or update the affected software if a patched version is available; otherwise, consider using an alternative product. 2) Implement prepared statements in the code to ensure user inputs like 'fname' are treated as data, not executable SQL. 3) Apply strict input validation and filtering on all user-supplied data. 4) Limit database user permissions by avoiding high-privilege accounts for routine operations. 5) Conduct regular security audits to detect and fix vulnerabilities promptly. Since no known countermeasures or patches are currently available, replacing the software or applying the above coding and configuration best practices is critical. [1, 3]