dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-14622

HIGH · 7.3 CVSS v3.1 Published 2026-07-04
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 7 weeks old

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 found in jairiidriss restaurant-website-php-mysql up to 521428b5b612449df0cf4a5d15ee40cba67f3d35. This vulnerability affects unknown code of the file /admin/ajax_files of the component AJAX Endpoint. Performing a manipulation results in missing authentication. The attack is possible to be carried out remotely. The exploit has been made public and could be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.

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 confidence

The restaurant-website-php-mysql project contains an authentication bypass vulnerability in the /admin/ajax_files AJAX endpoint. This endpoint, intended for administrative operations, can be accessed without any authentication credentials, allowing remote attackers to execute administrative functions without authorization. The exploit has been publicly disclosed, increasing the risk of active exploitation.

MitigationImplement proper authentication and session validation on all /admin/ajax_files endpoints and conduct a comprehensive audit of other admin endpoints for similar authentication bypass issues.

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 restaurant-website-php-mysql installation
    Search the web server document root for directories or files associated with the restaurant-website-php-mysql project, such as an 'admin' folder or files named 'ajax_files' within the web accessible path
    Affected if The application files are present on the server
  2. Verify the /admin/ajax_files endpoint exists
    Check for the existence of the /admin/ajax_files path (or ajax_files.php) in the web root directory structure
    Affected if The endpoint file exists in the deployed application
  3. Test unauthenticated access to the endpoint
    Send an HTTP request to the /admin/ajax_files endpoint (e.g., via curl or browser) without providing any authentication credentials, session cookies, or login tokens
    Affected if The endpoint returns a successful response or executes administrative functions without requiring authentication
  4. Inspect the endpoint source code for authentication logic
    Open the ajax_files file (or corresponding PHP script) and examine whether it contains any authentication checks, session validation, or privilege verification at the beginning of the script
    Affected if No authentication or session validation code is present at the start of the endpoint
  5. Audit other /admin/ endpoints for similar issues
    Review other administrative endpoints in the /admin/ directory to see if they also lack authentication checks, as the advisory notes similar bypasses may exist
    Affected if Other admin endpoints can be accessed without authentication

You are affected if the restaurant-website-php-mysql application is deployed and the /admin/ajax_files endpoint responds without requiring any authentication credentials.

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 proper authentication and session validation on all /admin/ajax_files endpoints and conduct a comprehensive audit of other admin endpoints for similar authentication bypass issues.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14622 — 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-14622 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