CVE-2025-9699
BaseFortify
Publication date: 2025-08-30
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 |
|---|---|---|
| razormist | online_polling_system | 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-9699 is a critical SQL injection vulnerability in the SourceCodester Online Polling System Code version 1.0, specifically in the /admin/checklogin.php file. The vulnerability occurs because the 'myusername' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact system security by allowing attackers to gain unauthorized access to the database. They can leak sensitive information, tamper with data, disrupt services, and potentially gain full control over the system. This poses a significant threat to business continuity and data integrity if not addressed. [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 checking for the presence of the vulnerable endpoint /admin/checklogin.php and testing the 'myusername' parameter for SQL injection. Attackers may use Google dorking with the query "inurl:admin/checklogin.php" to identify vulnerable targets. To detect exploitation attempts or test your system, you can use tools like sqlmap or manual curl commands to send crafted payloads to the 'myusername' parameter and observe the response for SQL errors or unexpected behavior. Example curl command to test for SQL injection: curl -X POST -d "myusername=' OR '1'='1" -d "mypassword=test" http://your-target-domain/admin/checklogin.php Monitoring web server logs for suspicious POST requests to /admin/checklogin.php with unusual input in 'myusername' can also help detect exploitation attempts. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to prevent SQL injection. - Apply strict input validation and filtering on the 'myusername' parameter to ensure it conforms to expected formats. - Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. - Conduct regular security audits of your code and systems to detect and address vulnerabilities promptly. - If possible, replace the affected component with an alternative product or update to a fixed version once available. - Monitor your system for suspicious activity targeting /admin/checklogin.php and respond accordingly. [2, 3]