Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess admin login page
-
DeliveryInject SQL payload in email parameter
-
ExploitBypass authentication query logic
-
ExecutionGain administrative session
-
ImpactExtract database contents or modify records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Remote exploitation against default configurations of code-projects Feedback System 1.0 requires only that the /admin/checklogin.php endpoint be network-accessible - no authentication, user interaction, or non-default settings needed per CVSS vector AV:N/AC:L/PR:N/UI:N. The SQL injection occurs in the administrative login function itself, meaning the vulnerability exists before any authentication takes place. Exploitation is limited only by network reachability: instances behind IP restrictions, VPNs, or not exposed to internet are protected by network segmentation rather than application security. No specific PHP version, database backend (MySQL/MariaDB/PostgreSQL), or server configuration required - the vulnerable code logic triggers regardless of underlying stack. Deployment scenarios with administrative interfaces isolated on management VLANs or behind authentication proxies significantly reduce attack surface despite application-level vulnerability remaining unfixed. |
| Impact | Real-world risk is elevated due to convergence of multiple factors. CVSS 7.3 (High) with AV:N/AC:L/PR:N/UI:N indicates remote exploitation with no prerequisites - any internet-exposed instance is vulnerable. CVSS temporal metrics show E:P (Proof-of-concept exploit exists) and RL:X (no official fix information), confirming both exploit availability and absence of vendor remediation. The GitHub POC reference provides step-by-step exploitation instructions, making this accessible to low-skill attackers. Impact metrics (C:L/I:L/A:L) suggest partial confidentiality, integrity, and availability compromise - typical for authentication bypass leading to admin panel access. However, SQL injection frequently enables privilege escalation beyond CVSS-rated impact: attackers may extract entire databases, modify records, or use database features (xp_cmdshell, INTO OUTFILE) for server-level code execution. No CISA KEV listing suggests targeted rather than widespread mass exploitation, but small open-source projects often lack visibility into real-world attacks. Primary risk factors: public POC, authentication bypass target, likely abandoned project (code-projects.org hosts legacy PHP applications with irregular maintenance). CRITICAL GAP: No vendor advisory or patched version identified - remediation options limited to workarounds or application replacement. |
| Exploit ScenarioDerived | Attacker identifies internet-exposed Feedback System 1.0 instance through Shodan/Censys search for characteristic HTTP headers or file paths. Navigates to /admin/checklogin.php and intercepts login POST request. Modifies email parameter to SQL injection payload such as ' OR '1'='1' -- to bypass authentication logic, gaining immediate administrative access. From compromised admin panel, attacker exports user feedback data containing PII, injects malicious JavaScript into feedback templates for stored XSS attacks against legitimate administrators, or leverages additional vulnerabilities to establish persistent backdoor. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 07, 2026
SQL injection in code-projects Feedback System 1.0 admin login panel allows remote unauthenticated attackers to bypass authentication and access administrative functions via crafted email parameter. Publicly available proof-of-concept exploit code exists on GitHub. CVSS 7.3 (High) with network vector and low complexity indicates straightforward exploitation requiring no special configuration. EPSS data not provided, but public POC significantly lowers exploitation barrier for opportunistic attacks against internet-exposed instances.
RemediationAI
No vendor-released patch identified at time of analysis - code-projects.org provides no security advisories and the project appears unmaintained based on lack of official response to public vulnerability disclosure. Primary remediation is application replacement with actively maintained feedback management software. If immediate replacement is not feasible, implement these compensating controls with noted trade-offs: (1) Deploy web application firewall with SQL injection signatures targeting the /admin/checklogin.php endpoint - may require custom rules for 'email' parameter, introduces latency and potential false positives blocking legitimate logins. (2) Restrict network access to /admin/ directory using IP allowlisting at web server or firewall level - limits admin access to trusted networks only, breaks remote administration workflows. (3) Place application behind authentication proxy (e.g., Authelia, oauth2-proxy) requiring separate credential verification before reaching vulnerable code - adds architectural complexity and single point of failure. (4) Monitor database query logs for UNION, OR 1=1, comment sequences (--,#,/**/) in email field submissions - detection only, does not prevent exploitation. All workarounds are temporary measures; plan migration to supported software. Review database access logs for indicators of prior compromise: unexpected admin logins, bulk SELECT queries from web application account, new administrative users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a classic SQL injection vulnerability (CWE-89) in a PHP-based application. The /admin/checklogin.php endpoint - responsible for administrative authentication - fails to properly sanitize or parameterize the 'email' input parameter before incorporating it into SQL queries. Code-projects Feedback System 1.0 is a lightweight open-source PHP application for managing user feedback, commonly deployed on LAMP/WAMP stacks. The vulnerability resides in the authentication logic itself, meaning attackers can manipulate SQL queries to bypass credential verification, enumerate database contents, or potentially escalate to full database compromise depending on database permissions and configuration.
Know when Feedback System gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
A security vulnerability has been detected in code-projects Feedback System 1.0. Impacted is an unknown function of the file /admin/checklogin.php. Such manipulation of the argument email leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used.
Executive ViewAI
CVE-2026-8098 is a critical authentication bypass in code-projects Feedback System 1.0 that allows unauthenticated attackers to gain administrative access through SQL injection in the login panel. Organizations running this software with internet-facing deployments face immediate risk of full administrative compromise, enabling data theft, system manipulation, and lateral movement. Public exploit code availability significantly increases the likelihood of opportunistic attacks.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict network access to admin login panel via firewall rules, IP whitelisting, or VPN-only access; (2) Deploy Web Application Firewall with SQL injection signatures targeting the email parameter; (3) Disable the feedback system entirely if not critical to operations; (4) Monitor authentication logs for anomalous admin logins and database query patterns; (5) Establish incident response procedures for potential compromise of instances exposed before mitigation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-28444
GHSA-g323-63gp-7v74
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB