CVE Alert: CVE-2025-10673 – itsourcecode – Student Information Management System
CVE-2025-10673
A vulnerability was determined in itsourcecode Student Information Management System 1.0. The impacted element is an unknown function of the file /admin/modules/class/index.php. This manipulation of the argument classId causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized.
AI Summary Analysis
Risk verdict
High risk: remote, unauthenticated SQL injection with publicly disclosed exploit increases likelihood of rapid compromise.
Why this matters
The vulnerability enables data exfiltration or alteration from student records and could enable further footholds in affected environments. Public disclosure lowers the barrier for opportunistic attackers and reduces the window for defender preparation.
Most likely attack path
An attacker can reach a network-exposed web endpoint without authentication, send crafted input to trigger SQL injection, and read or modify backend data. With no user interaction required and low attack complexity, the attacker could achieve data leakage and possibly data integrity impacts; overall impact remains local to the targeted database scope unless expanded.
Who is most exposed
Entities hosting this web-based system on internet-facing servers—common in small/medium educational deployments or poorly segregated hosting—are at highest risk, especially where admin interfaces are accessible from outside the perimeter.
Detection ideas
- Web server/app logs show repeated, abnormal input attempts targeting the vulnerable endpoint.
- Presence of SQL error messages or database error codes in responses.
- Unusual spikes in read-access to student records or related tables.
- Payload patterns typical of SQLi (tautologies, union-based payloads) in input fields.
- IDS/WAF alerts for SQL injection signatures or anomalous query structures.
Mitigation and prioritisation
- Apply vendor patch or upgrade to a fixed version as a priority.
- Enforce parameterised queries and strict input validation in the vulnerable component.
- Implement WAF/IDS rules to block SQLi patterns; enable automated alerts.
- Harden access to admin surfaces: require authentication, MFA, and network-based access controls; restrict admin from internet exposure where feasible.
- Conduct change management and testing before deploying fixes to production.
Note: treat as priority 1 if KEV is true or EPSS ≥ 0.5.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below
To keep up to date follow us on the below channels.