CVE-2026-0850VulnerabilityPublished 11 Jan 2026Updated 23 Feb 2026

CVE-2026-0850: 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 11 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-0850, organizations should immediately review and sanitize all inputs to the /admin/delete_activity.php endpoint, particularly the activity_id parameter. Implement parameterized queries or prepared statements to prevent SQL injection. Restrict access to administrative functions strictly to trusted users and enforce the principle of least privilege to minimize the risk of exploitation by insiders. Conduct thorough code audits to identify and remediate similar vulnerabilities elsewhere in the application. Monitor database logs for unusual queries or patterns indicative of injection attempts. If a patch becomes available from the vendor, apply it promptly. Additionally, consider deploying web application firewalls (WAFs) with SQL injection detection rules as a temporary protective measure. Educate administrators about secure coding practices and the risks of SQL injection to prevent recurrence.

Description

A vulnerability was determined in code-projects Intern Membership Management System 1.0. Impacted is an unknown function of the file /admin/delete_activity.php. Executing a manipulation of the argument activity_id can lead to sql injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The SQL injection vulnerability can lead to unauthorized access to sensitive intern membership data, including personal information and activity logs. Attackers exploiting this flaw could manipulate or delete critical records, undermining data integrity and potentially disrupting membership management operations. This could result in data breaches, loss of trust, regulatory penalties, and operational downtime. Since the vulnerability requires high privileges, the impact is somewhat contained to insiders or compromised accounts with elevated access, but the risk remains significant in environments where privilege escalation is possible. The availability of the system could also be affected if attackers execute destructive SQL commands. Overall, the vulnerability poses a moderate risk to organizations relying on this software for managing intern memberships, especially those handling sensitive or regulated data.

Summary

CVE-2026-0850 identifies a SQL injection vulnerability in the code-projects Intern Membership Management System version 1.0, specifically in the /admin/delete_activity.php script. The vulnerability arises from insufficient input validation or sanitization of the activity_id parameter, which is used in SQL queries without proper escaping or parameterization. An attacker with high privileges can remotely manipulate this parameter to inject arbitrary SQL commands, potentially allowing unauthorized reading, modification, or deletion of database records. The vulnerability does not require user interaction but does require the attacker to have authenticated access with elevated privileges, which somewhat limits the attack vector. The CVSS 4.0 score of 5.1 reflects a medium severity, considering the ease of remote exploitation but the prerequisite of high privileges. No patches or fixes have been linked yet, and no known exploits are reported in the wild, but the public disclosure increases the likelihood of future exploitation attempts. The vulnerability impacts the confidentiality, integrity, and availability of the membership system's data, which could include sensitive intern or membership information. Organizations using this system should conduct immediate code reviews, implement input validation, and monitor for suspicious database activity to mitigate risks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats