Open Source Point Of Sale: Weak Password Requirements
CVE-2025-63800 is a high-severity weak password requirements vulnerability in Open Source Point Of Sale from Opensourcepos, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Open Source Point Of Sale versions: 3.4.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.48% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Open Source Point Of Sale you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Opensourcepos | Open Source Point Of Sale | 3.4.1 | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CISA (ADP).
Official description
The password change endpoint in Open Source Point of Sale 3.4.1 allows users to set their account password to an empty string due to missing server-side validation. When an authenticated user omits or leaves the `password` and `repeat_password` parameters empty in the password change request, the backend still returns a successful response and sets the password to an empty string. This effectively disables authentication and may allow unauthorized access to user or administrative accounts.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Weak Password Requirements
The product does not require that users should have strong passwords.
How developers prevent this class of flaw
- Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
- Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- github.com/omkaryepre/vulnerability-research/tree/main/CVE-2025-63800Exploit, Third Party Advisory
Other references
- github.com/opensourcepos/opensourceposProduct
- opensourcepos.org/Product
Other vulnerabilities in Open Source Point Of Sale
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.1 High severity
- 7.2 High severity
- 7.2 High severity
Recent Weak Password Requirements vulnerabilities
- 9.8 Critical severity
- 8.2 High severity
- 9.8 Critical severity
- 8.3 High severity
- 7.5 High severity
- 8.6 High severity
Spotted an error? Tell us.