VulnerabilityPublished 18 Nov 2025

CVE-2025-63800: Open Source Point of Sale · CVE-2025-63800 is a high-severity

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should immediately audit their Open Source POS deployments to identify affected versions, specifically version 3.4.1. Until an official patch is released, implement strict server-side validation to reject password change requests where the 'password' or 'repeat_password' fields are empty or do not meet complexity requirements. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious password change requests. Enforce multi-factor authentication (MFA) for administrative accounts to reduce the risk of unauthorized access. Conduct regular account audits to detect accounts with empty or weak passwords and reset them proactively. Educate users and administrators about the risk and encourage prompt reporting of suspicious account behavior. Monitor logs for anomalous password change activities. Plan for rapid deployment of official patches once available and test updates in controlled environments before production rollout. Lastly, review and enhance overall password policies and authentication mechanisms within the POS environment.

Description

CVE-2025-63800 is a high-severity vulnerability in Open Source Point of Sale (POS) version 3.4.1 where the password change endpoint allows setting an account password to an empty string due to missing server-side validation. Authenticated users can submit a password change request with empty 'password' and 'repeat_password' fields, and the backend will accept it, effectively disabling authentication for that account. This flaw can lead to unauthorized access to user or administrative accounts without requiring any privileges or user interaction. The vulnerability impacts confidentiality by allowing attackers to bypass authentication controls. No known exploits are currently reported in the wild. European organizations using this POS software are at risk, especially retail and hospitality sectors relying on Open Source POS. Mitigation requires immediate patching or implementing strict server-side validation to reject empty passwords. Countries with significant retail sectors using open-source POS solutions, such as Germany, France, and the UK, are likely most affected.

Impact

For European organizations, especially those in retail, hospitality, and other sectors using Open Source POS 3.4.1, this vulnerability poses a critical risk to account security. Attackers can bypass authentication controls by setting empty passwords, potentially gaining unauthorized access to sensitive customer data, transaction records, and administrative functions. This could lead to data breaches, fraud, and operational disruptions. The confidentiality of user and administrative accounts is severely compromised, increasing the risk of insider threats or external attackers manipulating POS systems. Given the widespread use of open-source POS solutions in European small and medium enterprises, the impact could be broad. Additionally, regulatory frameworks such as GDPR impose strict data protection requirements, and exploitation of this vulnerability could lead to compliance violations and financial penalties. The absence of integrity or availability impact limits the scope to unauthorized access and data confidentiality breaches, but these are critical in payment and customer data contexts.

CWE-521Weak Password Requirements (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not require that users should have strong passwords.
Architecture and Design
A product's design should require adherance to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes: Enforcement of a minimum and maximum length; Restrictions against password reuse; Restrictions against using…
Architecture and Design
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.
Implementation
Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.1.2 (opens in a new tab)
V2.1.4 (opens in a new tab)
V2.1.3 (opens in a new tab)
Attack patterns
Dictionary-based Password Attack (opens in a new tab)
Password Brute Forcing (opens in a new tab)
Kerberoasting (opens in a new tab)
Rainbow Table Password Cracking (opens in a new tab)
Remote Services with Stolen Credentials (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 25 Nov 2025, 17:17 UTC

WeaknessesCWE-521

Technical details

References

Community reviews

Related threats