CVE-2025-12938
BaseFortify
Publication date: 2025-11-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 |
|---|---|---|
| projectworlds | online_admission_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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?
CVE-2025-12938 is a critical SQL injection vulnerability in Projectworlds Online Admission System 1.0, specifically in the /process_login.php file. It occurs because the 'keywords' parameter is not properly validated, allowing attackers to inject malicious SQL code. This can be exploited remotely to gain unauthorized access to the database. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized modification, deletion, and exposure of sensitive data stored in the database. Attackers can manipulate the database remotely without authentication, potentially compromising system security and data integrity. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for suspicious SQL injection attempts targeting the '/process_login.php' endpoint, specifically looking for unusual or malicious input in the 'keywords' parameter. You can use web application firewall (WAF) logs or intrusion detection system (IDS) signatures to identify such attempts. Additionally, manual testing with SQL injection payloads against the 'keywords' parameter can help confirm the vulnerability. For example, using curl to send test payloads: curl -X POST -d "keywords=' OR '1'='1" https://yourserver/process_login.php or using sqlmap to test the parameter: sqlmap -u "https://yourserver/process_login.php" --data="keywords=test" -p keywords --batch [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying proper input validation and sanitization on the 'keywords' parameter in '/process_login.php' to prevent SQL injection. Use prepared statements or parameterized queries to handle user inputs safely. If a patch or update is available from the vendor, apply it promptly. Additionally, restrict database permissions to limit the impact of potential exploitation and monitor logs for suspicious activity related to this endpoint. [1]