Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13289: SQL Injection in 1000projects Design & Development of Student Database Management System

0
Medium
VulnerabilityCVE-2025-13289cvecve-2025-13289
Published: Mon Nov 17 2025 (11/17/2025, 16:02:05 UTC)
Source: CVE Database V5
Vendor/Project: 1000projects
Product: Design & Development of Student Database Management System

Description

A vulnerability was detected in 1000projects Design & Development of Student Database Management System 1.0. Affected is an unknown function of the file /TeacherLogin/Academics/SubjectDetails.php. The manipulation of the argument SubCode results in sql injection. The attack may be performed from remote. The exploit is now public and may be used.

AI-Powered Analysis

AILast updated: 11/17/2025, 16:25:12 UTC

Technical Analysis

CVE-2025-13289 is an SQL injection vulnerability identified in the 1000projects Design & Development of Student Database Management System version 1.0. The vulnerability resides in the /TeacherLogin/Academics/SubjectDetails.php script, specifically in the handling of the SubCode parameter. Due to inadequate input sanitization, an attacker can manipulate this parameter to inject arbitrary SQL commands. This injection flaw allows remote attackers to execute unauthorized queries on the backend database without requiring user interaction, although low privileges are necessary to access the vulnerable function. The impact includes potential unauthorized disclosure, modification, or deletion of student records and academic data, compromising confidentiality, integrity, and availability of the system. The vulnerability is publicly disclosed with exploit code available, increasing the likelihood of exploitation. No patches have been officially released yet, and no active exploitation has been reported. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). This vulnerability highlights the importance of secure coding practices in educational management systems, which often contain sensitive personal and academic information.

Potential Impact

For European organizations, particularly educational institutions using the affected Student Database Management System, this vulnerability poses a significant risk to the confidentiality and integrity of student and academic data. Exploitation could lead to unauthorized access to sensitive personal information, academic records, and potentially allow attackers to alter or delete critical data. This could result in reputational damage, legal liabilities under GDPR due to data breaches, and disruption of academic operations. The availability impact is moderate but could escalate if attackers leverage the vulnerability to perform denial-of-service attacks or corrupt data. Given the public availability of exploit code, the risk of targeted attacks against European educational entities is heightened. Institutions relying on this software without adequate security controls or patches are vulnerable to remote exploitation, which could compromise large datasets and affect multiple stakeholders including students, faculty, and administrative staff.

Mitigation Recommendations

1. Immediate implementation of input validation and sanitization on the SubCode parameter to prevent SQL injection. Use parameterized queries or prepared statements in the codebase. 2. Restrict database user permissions to the minimum necessary, preventing unauthorized data manipulation even if injection occurs. 3. Monitor network traffic and application logs for unusual SQL queries or access patterns indicative of exploitation attempts. 4. Isolate the affected system within the network to limit exposure until a patch or update is available. 5. Educate developers and administrators on secure coding practices and the risks of SQL injection vulnerabilities. 6. Develop and deploy a custom patch or workaround if official patches are not yet available, such as input filtering at the web application firewall (WAF) level. 7. Conduct regular security assessments and penetration testing focused on injection flaws. 8. Prepare an incident response plan specific to potential data breaches involving student information. 9. Engage with the vendor or community to track patch releases and apply updates promptly once available.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-11-17T07:55:03.235Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 691b4a4dbf18c64a4b316bf3

Added to database: 11/17/2025, 4:16:13 PM

Last enriched: 11/17/2025, 4:25:12 PM

Last updated: 11/17/2025, 7:00:04 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats