CVE-2026-8098
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the email parameter of /admin/checklogin.php in code-projects Feedback System 1.0 allows remote attackers to inject malicious SQL queries via the login form. The attack requires no authentication and the exploit is publicly available.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Feedback System installationSearch the filesystem for the 'checklogin.php' file in an 'admin' directory, typically under a web root. Common paths include /var/www/html/feedback-system/admin/checklogin.php or C:\inetpub\wwwroot\feedback-system\admin\checklogin.phpAffected if The file /admin/checklogin.php exists and belongs to the code-projects Feedback System version 1.0
-
Verify the application versionCheck for version identifiers in the application - look for a version.php file, readme.txt, or any file containing '1.0' or 'Feedback System' within the application directory structureAffected if The installed version is Feedback System 1.0 (no other version range provided)
-
Confirm the vulnerable parameter existsOpen /admin/checklogin.php and locate the code handling the 'email' POST or GET parameter in the login form. Look for direct inclusion of this parameter in SQL queries without prepared statementsAffected if The email parameter is directly concatenated into an SQL query without parameterization
-
Assess network accessibilityDetermine if the /admin/checklogin.php endpoint is accessible over the network. Check web server configuration for the application path and verify the /admin directory is not restricted by IP or authenticationAffected if The /admin/checklogin.php endpoint is reachable from the network without authentication
You are affected if the code-projects Feedback System 1.0 is installed with the checklogin.php file accessible and the email parameter is used in unprotected SQL query construction.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries in checklogin.php with prepared statements/parameterized queries, or implement input validation and output escaping. Audit other files in the application for similar SQL injection vulnerabilities.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8098 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8098 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data