CVE-2025-8247
BaseFortify
Publication date: 2025-07-28
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-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-8247 is a critical SQL injection vulnerability in Projectworlds Online Admission System version 1.0, specifically in the /admin.php file. The vulnerability arises from improper handling and insufficient input validation of the 'markof' parameter, which is directly used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, leading to unauthorized database access, data leakage, data manipulation, and potentially full system control or service disruption. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to view, modify, or delete sensitive information. It can compromise the confidentiality, integrity, and availability of the system. Attackers may gain full control over the system or disrupt services, causing significant operational and security impacts. [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 testing the 'markof' parameter in the /admin.php file for SQL injection. One method is to use time-based blind SQL injection payloads, such as: markof=' AND (SELECT 3114 FROM (SELECT(SLEEP(5)))NBAj) AND 'TECb'='TECb, which causes a delay if vulnerable. Additionally, automated tools like sqlmap can be used to test the URL with POST data containing the 'markof' parameter. Google dorking with queries like inurl:admin.php can help identify vulnerable targets on the network. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Enforcing strict input validation and filtering on the 'markof' parameter to ensure inputs conform to expected formats. 3) Restricting database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. 4) Conducting regular security audits of code and systems to detect and remediate vulnerabilities promptly. If possible, replacing the affected software with an alternative product is also suggested. [2, 3, 1]