CVE-2026-0697VulnerabilityPublished 8 Jan 2026Updated 23 Feb 2026

CVE-2026-0697: code-projects Intern Membership Management System · SQL Injection

Affects code-projects Intern Membership Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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 8 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-25.

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
code-projectsIntern Membership Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-0697, organizations should implement the following specific measures: 1) Immediately restrict access to the /intern/admin/edit_admin.php endpoint to trusted administrators only, using network segmentation and access control lists. 2) Apply strict input validation and sanitization on the admin_id parameter to ensure only expected numeric or alphanumeric values are accepted. 3) Refactor the vulnerable code to use parameterized SQL queries or prepared statements to eliminate injection vectors. 4) Monitor logs for unusual SQL errors or suspicious activity targeting the admin_id parameter. 5) If possible, upgrade to a patched version once available or apply vendor-provided patches promptly. 6) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this endpoint. 7) Conduct regular security assessments and code reviews focusing on input handling in administrative modules. 8) Educate administrators on the risks of SQL injection and the importance of secure credential management to prevent privilege escalation.

Description

A flaw has been found in code-projects Intern Membership Management System 1.0. The impacted element is an unknown function of the file /intern/admin/edit_admin.php. This manipulation of the argument admin_id causes sql injection. The attack may be initiated remotely. The exploit has been published and may be used.

Impact

The SQL injection vulnerability in the Intern Membership Management System can have significant impacts on organizations using this software. Attackers with high privileges can exploit the flaw to execute arbitrary SQL commands, potentially leading to unauthorized disclosure of sensitive membership data, modification or deletion of records, and disruption of system availability. This can result in data breaches, loss of trust, regulatory penalties, and operational downtime. Since the system manages membership information, the exposure of personally identifiable information (PII) or internal administrative data could have privacy and compliance implications. The remote exploitability without user interaction increases the risk of automated attacks once exploit code becomes widespread. Organizations relying on this system for critical membership management functions may face operational and reputational damage if the vulnerability is exploited.

Summary

CVE-2026-0697 identifies a SQL injection vulnerability in the code-projects Intern Membership Management System version 1.0. The vulnerability resides in the /intern/admin/edit_admin.php file, where the admin_id parameter is improperly sanitized, allowing an attacker to inject malicious SQL commands. This flaw can be exploited remotely without user interaction, but requires high privileges (likely administrative access) to trigger. The injection can lead to unauthorized data access, modification, or deletion, compromising the confidentiality, integrity, and availability of the membership management system's database. The vulnerability has been assigned a CVSS 4.0 score of 5.1, indicating medium severity, primarily because exploitation requires privileged access but no user interaction or complex attack vectors. Although no active exploitation has been reported, the availability of exploit code increases the risk of future attacks. The lack of official patches or mitigations at the time of disclosure necessitates immediate defensive measures by system administrators. The vulnerability highlights the importance of secure coding practices such as input validation and use of parameterized queries to prevent SQL injection attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:19 UTC

Technical details

References

Community reviews

Related threats