CVE-2026-1119VulnerabilityPublished 18 Jan 2026Updated 23 Feb 2026

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

Affects itsourcecode Society Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% 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 18 Jan 2026
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 2026-10-26.

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

Affected software

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

AI-suggested

To mitigate CVE-2026-1119, organizations should immediately implement the following measures: 1) Apply any available patches or updates from the vendor once released. 2) If patches are unavailable, implement web application firewall (WAF) rules to detect and block malicious SQL injection payloads targeting the activity_id parameter. 3) Conduct a thorough code review and refactor the vulnerable /admin/delete_activity.php script to use parameterized queries or prepared statements, ensuring proper input validation and sanitization. 4) Restrict access to the /admin directory by IP whitelisting or VPN to limit exposure. 5) Monitor database logs and application logs for suspicious queries or anomalies related to activity_id usage. 6) Educate administrators on the risk and signs of exploitation attempts. 7) Consider deploying runtime application self-protection (RASP) tools to detect and prevent injection attacks in real time. These steps go beyond generic advice by focusing on immediate protective controls and secure coding practices tailored to this specific vulnerability.

Description

A flaw has been found in itsourcecode Society Management System 1.0. The affected element is an unknown function of the file /admin/delete_activity.php. Executing a manipulation of the argument activity_id can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published and may be used.

Impact

The impact of CVE-2026-1119 is significant for organizations using the itsourcecode Society Management System 1.0. Successful exploitation can lead to unauthorized access to sensitive community management data, including activity logs and user information. Attackers may manipulate or delete records, undermining data integrity and disrupting normal operations. Confidentiality breaches could expose personally identifiable information or internal administrative data. Availability may also be affected if attackers cause database errors or crashes. Given the remote, unauthenticated nature of the exploit, attackers can operate stealthily and at scale. This poses risks to municipalities, housing societies, or community organizations relying on this software for governance and communication. The presence of a public exploit increases the urgency for mitigation to prevent data breaches, reputational damage, and potential regulatory consequences related to data protection laws.

Summary

CVE-2026-1119 identifies a SQL injection vulnerability in the itsourcecode Society Management System version 1.0. The vulnerability exists in the /admin/delete_activity.php script, where the activity_id parameter is not properly sanitized or validated before being used in SQL queries. This allows an unauthenticated remote attacker to inject malicious SQL code by manipulating the activity_id argument. The injection flaw can be exploited to read, modify, or delete database records, potentially leading to unauthorized data disclosure, data corruption, or denial of service conditions. The vulnerability does not require any privileges or user interaction, making it easier to exploit remotely. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although no confirmed active exploitation has been reported, a public exploit is available, increasing the likelihood of attacks. The lack of official patches or updates from the vendor at this time further exacerbates the risk. This vulnerability highlights the importance of input validation and parameterized queries in web applications managing sensitive community data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:50 UTC

Technical details

References

Community reviews

Related threats