dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10704

HIGH · 7.3 CVSS v3.1 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was detected in SourceCodester Pizzafy E-Commerce System 1.0. Affected by this vulnerability is the function Login of the file /admin/admin_class_novo.php of the component Administrative Control Panel. The manipulation of the argument Username results in sql injection. The attack can be executed remotely. The exploit is now public 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 · high confidence

SQL injection vulnerability in the Login function of /admin/admin_class_novo.php in SourceCodester Pizzafy E-Commerce System 1.0. The Username parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries through the login form.

MitigationImplement prepared statements/parameterized queries for all SQL operations in the login function. Apply input validation and enforce least-privilege database accounts. If a vendor patch is available, apply it immediately.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable PHP file
    Check your web server document root for the existence of /admin/admin_class_novo.php. Common paths include /var/www/html/, /www/, or the webroot directory. Use: find /var/www -name 'admin_class_novo.php' 2>/dev/null
    Affected if The file admin_class_novo.php exists in the web directory tree, indicating the Pizzafy application is installed.
  2. Confirm the application version
    Check for version indicators in the application. Look for a version.php file, README file, or check the source code header comments in admin_class_novo.php for version strings. Also check for version info in any installer or setup files.
    Affected if The installed version is Pizzafy E-Commerce System 1.0, matching the affected version range.
  3. Verify the admin login endpoint is accessible
    Confirm the /admin/ login interface is reachable. Test accessing http://yourdomain/admin/ or http://yourdomain/admin/login.php (or similar) to verify the login page is publicly or internally accessible.
    Affected if The admin login page is accessible, enabling the vulnerable Username parameter to be reached by an attacker.
  4. Inspect the SQL query handling in the login function
    Open admin_class_novo.php and locate the login function. Search for SQL queries involving the Username parameter. Check if the query directly concatenates user input without using prepared statements or parameterized queries.
    Affected if The code shows direct string concatenation of the Username parameter into SQL queries without sanitization or parameterization, confirming the vulnerability exists.
  5. Check for WAF or input filtering protections
    Review any web application firewall configurations, input validation middleware, or security plugins that may be processing the Username parameter before it reaches the PHP code.
    Affected if No WAF, input filtering, or other protective layer is present between the user input and the vulnerable login function.

Your environment is affected if you have Pizzafy E-Commerce System 1.0 installed with the admin_class_novo.php file present and the admin login endpoint accessible, where the Username parameter is processed through unsanitized SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all SQL operations in the login function. Apply input validation and enforce least-privilege database accounts. If a vendor patch is available, apply it immediately.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10704 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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