VulnerabilityPublished 27 Oct 2025

CVE-2025-12277: Abdullah-Hasan-Sajjad Online-School · SQL Injection

Affects Abdullah-Hasan-Sajjad Online-SchoolSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediately implement input validation and sanitization on all user-supplied data, especially the Email parameter in /studentLogin.php, to prevent injection of malicious SQL code. 2. Refactor database queries to use parameterized statements or prepared queries, eliminating direct concatenation of user inputs into SQL commands. 3. Deploy Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the vulnerable endpoint. 4. Conduct thorough code reviews and security testing of the entire application to identify and remediate any additional injection points. 5. Monitor database logs and application logs for unusual query patterns or failed login attempts indicative of exploitation attempts. 6. Isolate the affected application environment and restrict database user privileges to the minimum necessary to limit potential damage. 7. Engage with the vendor or community to track patch releases or updates and plan for timely application of official fixes once available. 8. Educate IT and security teams on the vulnerability details and ensure incident response plans include scenarios involving SQL injection attacks on educational platforms.

Description

A flaw has been found in Abdullah-Hasan-Sajjad Online-School up to f09dda77b4c29aa083ff57f4b1eb991b98b68883. This affects an unknown part of the file /studentLogin.php. This manipulation of the argument Email causes sql injection. The attack is possible to be carried out remotely. The exploit has been published and may be used. This product adopts a rolling release strategy to maintain continuous delivery The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, this vulnerability presents a significant risk to the confidentiality and integrity of student and staff data managed by the affected online school platform. Exploitation could lead to unauthorized access to personal information, academic records, and potentially financial data, resulting in privacy breaches and reputational damage. The integrity of educational records could be compromised, affecting academic outcomes and trust in the institution. Availability impacts could disrupt online learning services, causing operational downtime and affecting students' education continuity. Additionally, organizations may face regulatory penalties under GDPR due to inadequate protection of personal data. The public availability of exploit code increases the risk of opportunistic attacks, especially targeting institutions with limited cybersecurity resources. The lack of vendor response and patch availability exacerbates the threat, requiring organizations to implement compensating controls promptly.

Summary

CVE-2025-12277 identifies a SQL injection vulnerability in the Abdullah-Hasan-Sajjad Online-School software, specifically in the /studentLogin.php endpoint where the Email parameter is vulnerable to injection attacks. This vulnerability arises due to insufficient input validation and improper handling of user-supplied data, allowing attackers to manipulate SQL queries executed by the backend database. The attack vector is network-based (AV:N), requiring no privileges (PR:N), no user interaction (UI:N), and no authentication, making it remotely exploitable by any unauthenticated attacker. The vulnerability impacts confidentiality, integrity, and availability with low vector and impact complexity, as indicated by the CVSS 4.0 vector (VC:L/VI:L/VA:L). Public exploit code has been published, increasing the likelihood of exploitation. The vulnerability could allow attackers to extract sensitive student data, modify records, or disrupt service availability, posing significant risks to educational institutions relying on this platform. Given the nature of the software—an online school platform—the impact extends to privacy violations and potential regulatory non-compliance under data protection laws such as GDPR.

References

Community reviews

Loading reviews…