opensourcepos Open Source Point of Sale up to 3.4.2 Login Endpoint app/Config/Filters.php Login::index excessive authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 1.43 |
Summary
A vulnerability has been found in opensourcepos Open Source Point of Sale up to 3.4.2 and classified as problematic. This vulnerability affects the function Login::index of the file app/Config/Filters.php of the component Login Endpoint. This manipulation causes excessive authentication.
This vulnerability is registered as CVE-2026-19895. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in opensourcepos Open Source Point of Sale up to 3.4.2. It has been declared as problematic. Affected by this vulnerability is the function Login::index of the file app/Config/Filters.php of the component Login Endpoint. The manipulation with an unknown input leads to a excessive authentication vulnerability. The CWE definition for the vulnerability is CWE-307. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. As an impact it is known to affect confidentiality.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-19895. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet. By approaching the search of inurl:app/Config/Filters.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.7
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Excessive authenticationCWE: CWE-307 / CWE-799 / CWE-400
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/14/2026 Advisory disclosed08/14/2026 VulDB entry created
08/14/2026 VulDB entry last update
Sources
Advisory: 4583Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-19895 (🔒)
GCVE (CVE): GCVE-0-2026-19895
GCVE (VulDB): GCVE-100-390085
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/14/2026 20:57Changes: 08/14/2026 20:57 (60)
Complete: 🔍
Submitter: ZAST.AI
Cache ID: 216::103
Submit
Accepted
- Submit #870664: OpenSourcePOS <=3.4.2 Improper Restriction of Excessive Authentication Attempts (by ZAST.AI)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.