VulnerabilityPublished 20 Aug 2025

CVE-2025-9238: Swatadru Exam-Seating-Arrangement · SQL Injection

Affects Swatadru Exam-Seating-ArrangementSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 12:29 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 27% 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 20 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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 or the CVSS exploit maturity 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

Given the absence of official patches, European organizations should implement immediate compensating controls. These include deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'email' parameter in /student.php requests. Conduct thorough input validation and sanitization on all user-supplied data, especially email fields, using parameterized queries or prepared statements if source code access is available. Monitor application logs for suspicious query patterns or repeated failed login attempts. Restrict network access to the application backend where feasible, limiting exposure to trusted IP ranges. Engage in active threat hunting for indicators of compromise related to this vulnerability. Additionally, organizations should consider isolating or temporarily disabling the affected Student Login component until a vendor patch or update is released. Finally, maintain regular backups of critical data to enable recovery in case of data manipulation or loss.

Description

A vulnerability was determined in Swatadru Exam-Seating-Arrangement up to 97335ccebf95468d92525f4255a2241d2b0b002f. Affected is an unknown function of the file /student.php of the component Student Login. Executing manipulation of the argument email can lead to sql injection. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, particularly educational institutions and examination boards using Swatadru Exam-Seating-Arrangement software, this vulnerability poses significant risks. Exploitation could lead to unauthorized disclosure of personally identifiable information (PII) such as student emails and credentials, violating GDPR and other data protection regulations. Integrity of exam seating data could be compromised, potentially enabling fraud or disruption of examination logistics. Availability impacts are limited but could arise if attackers manipulate database queries to cause application errors or downtime. The lack of vendor response and patch availability increases exposure duration, raising the likelihood of targeted attacks. Institutions relying on this software for critical examination scheduling may face operational disruptions and reputational damage if exploited.

Summary

CVE-2025-9238 is a SQL Injection vulnerability identified in the Swatadru Exam-Seating-Arrangement software, specifically within the /student.php file in the Student Login component. The vulnerability arises from improper sanitization or validation of the 'email' argument, allowing an attacker to manipulate SQL queries executed by the application. This flaw enables remote attackers to inject malicious SQL code without requiring authentication or user interaction, potentially leading to unauthorized data access or modification. The product uses a rolling release model, which complicates pinpointing affected versions beyond the provided commit hash (97335ccebf95468d92525f4255a2241d2b0b002f). The vendor has not responded to disclosure attempts, and no patches or updates have been made publicly available. The CVSS v4.0 score is 6.9 (medium severity), reflecting the network attack vector, no required privileges or user interaction, and limited impact on confidentiality, integrity, and availability. Although no known exploits are currently observed in the wild, the public disclosure of the vulnerability increases the risk of exploitation. The vulnerability could allow attackers to extract sensitive student data, alter seating arrangements, or disrupt examination processes by manipulating backend databases.

References

Community reviews

Loading reviews…