VulnerabilityPublished 2 Mar 2026

CVE-2026-3410: itsourcecode Society Management System · SQL Injection

Affects itsourcecode Society Management SystemSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 29 Oct 2026, 19:04 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 31% 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 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
itsourcecodeSociety Management System	Affected =1.0	Fixed in–

AI-suggested

Given the absence of an official patch, organizations should implement immediate compensating controls to mitigate CVE-2026-3410. First, apply strict input validation and sanitization on the student_id parameter at the web application firewall (WAF) or reverse proxy level to block malicious SQL payloads. Employ parameterized queries or prepared statements in the application code to prevent injection if source code access and modification are possible. Restrict access to the /admin/check_studid.php endpoint by IP whitelisting or VPN-only access to reduce exposure. Monitor web server and database logs for unusual query patterns or repeated failed attempts targeting student_id parameters. Regularly back up databases and verify backup integrity to enable recovery in case of data tampering. Engage with the vendor for updates or patches and plan for an upgrade or replacement of the vulnerable system. Finally, conduct security awareness training for administrators to recognize and respond to potential exploitation attempts.

Description

A weakness has been identified in itsourcecode Society Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/check_studid.php. Executing a manipulation of the argument student_id can lead to sql injection. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The impact of CVE-2026-3410 on organizations using the itsourcecode Society Management System 1.0 can be significant. Successful exploitation could lead to unauthorized disclosure of sensitive information stored in the database, including potentially personal or organizational data. Attackers might also alter or delete critical records, undermining data integrity and operational reliability. The availability of the system could be affected if malicious queries cause database crashes or lockups. Since the vulnerability is remotely exploitable without authentication or user interaction, attackers can launch automated attacks at scale, increasing the risk of widespread compromise. Organizations relying on this software for managing society or community data may face reputational damage, regulatory penalties, and operational disruptions if exploited. The absence of patches means that without mitigation, the risk remains high, especially as exploit code is publicly accessible.

Summary

CVE-2026-3410 is a SQL injection vulnerability identified in itsourcecode Society Management System version 1.0, specifically within the /admin/check_studid.php script. The vulnerability arises from improper sanitization or validation of the student_id parameter, which an attacker can manipulate to inject malicious SQL queries. This injection flaw allows remote attackers to execute arbitrary SQL commands against the backend database without requiring any authentication or user interaction, making exploitation straightforward. The CVSS 4.0 base score is 6.9 (medium), reflecting the ease of remote exploitation and the potential impact on confidentiality, integrity, and availability, though with limited scope and no privilege or user interaction requirements. The vulnerability has been publicly disclosed, and exploit code is available, although no active exploitation in the wild has been reported yet. The lack of official patches or mitigation guidance from the vendor increases the urgency for organizations to implement compensating controls. This vulnerability could enable attackers to extract sensitive data, modify or delete records, or disrupt normal database operations, severely impacting the affected organization's data security posture.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Mar 2026, 05:10 UTC

Technical details

References

Community reviews

Related threats