CVE-2025-10076
BaseFortify
Publication date: 2025-09-08
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?
This vulnerability is a SQL injection flaw in the Online Polling System version 1.0, specifically in the 'manage-profile.php' file. It occurs because the application directly uses user input from the 'email' parameter in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code, potentially manipulating the database unauthorizedly. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, leakage of sensitive information, data tampering, full system compromise, and potential disruption of services. This severely impacts system security and business continuity. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'email' parameter in the /manage-profile.php file for SQL injection flaws. One approach is to send crafted HTTP POST requests with SQL injection payloads in the 'email' parameter and observe the application's response for errors or unexpected behavior. For example, using curl to send a test payload: curl -X POST -d "email=' OR '1'='1" https://targetsite/manage-profile.php. Additionally, monitoring logs for unusual database errors or suspicious input patterns can help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'email' parameter to ensure it matches expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine database operations. 4) Conduct regular security audits of the code and system to identify and fix vulnerabilities promptly. [1]