CVE-2025-10077
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?
CVE-2025-10077 is a critical SQL injection vulnerability in SourceCodester Online Polling System version 1.0, specifically in the /registeracc.php file. The vulnerability occurs because the 'email' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely, which can manipulate the database by retrieving, modifying, or deleting data without authorization. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, allowing attackers to retrieve sensitive information, tamper with data, disrupt services, or even fully compromise the system. Because the attack can be launched remotely without authentication, it poses significant risks to system security and business continuity. [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 file /registeracc.php in the SourceCodester Online Polling System 1.0 and testing the 'email' parameter for SQL injection. One method is to use Google Dorking with queries like "inurl:registeracc.php" to identify potentially vulnerable targets. Additionally, sending crafted HTTP POST requests with SQL injection payloads in the 'email' parameter can help verify the vulnerability. Network or system scanning tools that detect SQL injection vulnerabilities or manual testing with tools like sqlmap targeting the 'email' parameter in /registeracc.php can be used. [3, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'email' parameter, and limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Regular security audits of code and systems should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected software with an alternative product is suggested. [2, 3, 1]