CVE-2026-109114: AdithyaYelloju Restaurant-Management-System Login Form login.php improper authentication

Published Oct 13, 2026
·
Updated

A vulnerability has been found in AdithyaYelloju Restaurant-Management-System up to 7f0e7e84255e8fcfd488e83f8f91451bbbff6b9c. This vulnerability affects unknown code of the file User/login.php of the component Login Form. Such manipulation of the argument email/passwd leads to improper authentication. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.

Affected Software

1 affected component
AdithyaYelloju Restaurant-Management-System<=7f0e7e84255e8fcfd488e83f8f91451bbbff6b9c

Event History

Oct 13, 2026
CVE Published
via MITRE·08:15 AM
Data Sourced
via MITRE·08:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments of AdithyaYelloju Restaurant-Management-System that include the affected User/login.php login form are exposed, including systems reachable remotely. The affected code is identified through commit 7f0e7e84255e8fcfd488e83f8f91451bbbff6b9c rather than a numbered release.

2

What does an attacker need to exploit it?

An attacker can exploit the issue remotely by manipulating the email and passwd arguments submitted to the login form. No privileges or user interaction are required according to the supplied severity vector.

3

Is public exploit information available?

Yes. The exploit has been publicly disclosed and may be used.

4

How can I determine whether my deployment is affected?

Check whether your deployment uses the Restaurant-Management-System User/login.php login form and compare its source history with the identified affected commit. Numbered affected or fixed versions are not available because the project uses rolling releases.

5

What should I do if no update is available?

No vendor response or fixed release is reported. If immediate patching is not possible, restrict remote access to the login endpoint as an exposure-reduction measure and review authentication activity for suspicious login behavior.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203