Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0699: SQL Injection in code-projects Intern Membership Management System

0
Medium
VulnerabilityCVE-2026-0699cvecve-2026-0699
Published: Thu Jan 08 2026 (01/08/2026, 06:32:05 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: Intern Membership Management System

Description

A vulnerability was found in code-projects Intern Membership Management System 1.0. This impacts an unknown function of the file /intern/admin/edit_activity.php. Performing a manipulation of the argument activity_id results in sql injection. Remote exploitation of the attack is possible. The exploit has been made public and could be used.

AI-Powered Analysis

AILast updated: 01/08/2026, 06:49:33 UTC

Technical Analysis

CVE-2026-0699 identifies a SQL injection vulnerability in the code-projects Intern Membership Management System version 1.0, specifically within the /intern/admin/edit_activity.php script. The vulnerability stems from insufficient input validation or sanitization of the activity_id parameter, which is manipulated by attackers to inject arbitrary SQL commands. This flaw allows remote attackers to execute unauthorized SQL queries on the backend database, potentially leading to unauthorized data disclosure, data modification, or even deletion. The vulnerability does not require user interaction or authentication, making it remotely exploitable over the network. The CVSS 4.0 vector indicates no privileges are required (PR:H means high privileges required, but the description says remote exploitation possible without authentication, so there is some ambiguity; however, the vector states PR:H, meaning some privileges are needed), no user interaction, and low impact on confidentiality, integrity, and availability individually, but combined they pose a moderate risk. The exploit code has been publicly disclosed, increasing the likelihood of exploitation attempts. No official patches or fixes have been linked yet, so organizations must implement mitigations proactively. The vulnerability affects only version 1.0 of the product, so upgrading or patching is critical. The Intern Membership Management System is likely used by organizations managing intern or membership data, making the exposure of sensitive personal or organizational data a significant concern.

Potential Impact

For European organizations, exploitation of this SQL injection vulnerability could lead to unauthorized access to sensitive intern or membership data, including personal identifiable information (PII), membership records, or administrative data. This could result in data breaches, regulatory non-compliance (e.g., GDPR violations), reputational damage, and potential financial penalties. The integrity of membership data could be compromised, leading to incorrect or malicious data modifications that affect organizational operations. Availability could also be impacted if attackers execute destructive SQL commands, causing service disruptions. Given the remote exploitability without user interaction, attackers could automate attacks at scale, increasing the risk for organizations using this system. The medium severity rating suggests a moderate but non-negligible risk, emphasizing the need for timely remediation to prevent escalation or lateral movement within networks.

Mitigation Recommendations

Organizations should immediately audit their use of the code-projects Intern Membership Management System version 1.0 and identify any instances of the vulnerable /intern/admin/edit_activity.php script. Specific mitigations include: 1) Implementing parameterized queries or prepared statements to prevent SQL injection; 2) Applying strict input validation and sanitization on the activity_id parameter and any other user-supplied inputs; 3) Restricting access to the administrative interface to trusted IP addresses or via VPN to reduce exposure; 4) Monitoring logs for suspicious SQL query patterns or unusual activity related to the edit_activity.php endpoint; 5) If possible, upgrading to a patched or newer version of the software once available; 6) Employing web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting this parameter; 7) Conducting regular security assessments and penetration tests focused on injection vulnerabilities; 8) Ensuring database accounts used by the application have the least privileges necessary to limit potential damage from exploitation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-01-07T21:38:59.696Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 695f5022c901b06321a78445

Added to database: 1/8/2026, 6:35:14 AM

Last enriched: 1/8/2026, 6:49:33 AM

Last updated: 1/9/2026, 3:07:54 AM

Views: 17

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats