CVE-2026-2083VulnerabilityPublished 7 Feb 2026Updated 23 Feb 2026

CVE-2026-2083: code-projects Social Networking Site · SQL Injection

Affects code-projects Social Networking SiteSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 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 7 Feb 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-projectsSocial Networking Site	Affected =1.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:code-projects:social_networking_site:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-2083, organizations should immediately audit the /delete_post.php script and any other code handling user input for SQL queries. The primary fix is to implement parameterized queries or prepared statements to ensure that user-supplied input is never directly concatenated into SQL commands. Input validation should be enforced to accept only expected data types and ranges for the 'ID' parameter. If vendor patches become available, they should be applied promptly. In the absence of official patches, temporary mitigations include restricting access to the vulnerable endpoint via network controls such as firewalls or web application firewalls (WAFs) configured to detect and block SQL injection patterns. Monitoring database logs for unusual queries and enabling alerting for suspicious activity can help detect exploitation attempts early. Additionally, organizations should consider upgrading to newer, secure versions of the software or migrating to alternative platforms if support is discontinued. Regular security assessments and code reviews are recommended to prevent similar vulnerabilities.

Description

A security flaw has been discovered in code-projects Social Networking Site 1.0. This affects an unknown function of the file /delete_post.php. Performing a manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks.

Impact

The potential impact of CVE-2026-2083 includes unauthorized disclosure of sensitive user data, data integrity violations through unauthorized modification or deletion of posts, and possible denial of service conditions if database operations are disrupted. For organizations running the affected version of the code-projects Social Networking Site, this could lead to reputational damage, loss of user trust, and regulatory compliance issues related to data protection. Attackers exploiting this vulnerability could gain access to backend databases, extract personal information, or manipulate content, which is particularly damaging for social networking platforms that rely on user-generated content and privacy. The ease of remote exploitation without authentication increases the threat level, especially for publicly accessible installations. Although the CVSS score is medium, the availability of a public exploit elevates the urgency for remediation to prevent potential widespread abuse.

Summary

CVE-2026-2083 identifies a SQL injection vulnerability in the code-projects Social Networking Site version 1.0, specifically within the /delete_post.php script. The vulnerability arises from improper sanitization of the 'ID' parameter, which is used in SQL queries without adequate validation or parameterization. This allows an unauthenticated remote attacker to inject malicious SQL code, potentially leading to unauthorized data access, modification, or deletion. The attack vector is network-based with no required privileges or user interaction, making exploitation straightforward once the vulnerable endpoint is accessible. The CVSS 4.0 score of 6.9 reflects a medium severity, with low to limited impact on confidentiality, integrity, and availability, but with a public exploit already available, the risk of exploitation increases. Although no active exploitation in the wild has been reported, the presence of a public exploit makes this vulnerability a credible threat. The lack of patches or vendor-provided fixes necessitates immediate mitigation efforts by users of this software. The vulnerability highlights the critical need for secure coding practices, especially input validation and the use of parameterized queries to prevent SQL injection attacks.

References

Community reviews

Loading reviews…