VulnerabilityPublished 30 Dec 2025

CVE-2025-15354: 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, 09:15 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 32% 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 30 Dec 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

Affected software

Product	Affected	Fixed in
itsourcecode Society Management System	Affected =1.0	Fixed in–

AI-suggested

Immediate mitigation steps include implementing strict input validation and sanitization on the Username parameter within /admin/add_admin.php, preferably by using parameterized queries or prepared statements to prevent SQL injection. Organizations should restrict access to the admin interface via network segmentation, VPNs, or IP whitelisting to reduce exposure. Monitoring database and application logs for suspicious queries or access patterns can help detect exploitation attempts early. If vendor patches or updates become available, they should be applied promptly. In the absence of official patches, consider deploying Web Application Firewalls (WAFs) with rules to detect and block SQL injection payloads targeting the vulnerable parameter. Conduct security audits and penetration tests focused on injection flaws to identify other potential weaknesses. Educate administrators on the risks and signs of exploitation. Finally, ensure regular backups of the database are maintained to enable recovery in case of data corruption or deletion.

Description

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

Impact

For European organizations, exploitation of this SQL injection vulnerability could result in unauthorized access to sensitive personal and administrative data stored within the Society Management System. This could lead to data breaches violating GDPR and other privacy regulations, resulting in legal and financial repercussions. Integrity of data could be compromised, allowing attackers to alter membership records or administrative credentials, potentially leading to unauthorized control over the system. Availability may also be impacted if attackers execute destructive SQL commands or cause database corruption. Organizations relying on this software for managing societies, housing associations, or community groups may face operational disruptions. The reputational damage from a breach could be significant, especially for entities handling sensitive resident or member information. Given the remote and unauthenticated nature of the exploit, attackers could target multiple organizations en masse, increasing the scale of impact across Europe.

Summary

The vulnerability identified as CVE-2025-15354 affects the itsourcecode Society Management System version 1.0. The issue resides in the /admin/add_admin.php script, where the Username parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This SQL injection vulnerability can be exploited remotely without requiring authentication or user interaction, making it highly accessible to attackers. Successful exploitation can lead to unauthorized data access, modification, or deletion within the underlying database, potentially compromising sensitive information managed by the system. The CVSS 4.0 score of 6.9 reflects a medium severity, indicating significant risk but not critical. The vulnerability does not require privileges or user interaction, and the attack complexity is low, increasing its threat potential. Although no active exploits have been reported in the wild, the availability of a public exploit increases the likelihood of future attacks. The lack of official patches or vendor advisories necessitates immediate defensive measures by users of the software. This vulnerability is particularly concerning for organizations managing community or society data, where confidentiality and integrity are paramount. The attack vector being network accessible further broadens the potential attack surface.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Dec 2025, 22:24 UTC

Technical details

References

Community reviews

Related threats