CVE-2025-63800VulnerabilityPublished 18 Nov 2025

Open Source Point of Sale · Password Change Endpoint

Source GCVE Database

Compare

Authoritative record:CVE-2025-63800· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 13 Nov 2026, 20:08 UTC

CVSS 3.1 base score

7.5High

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

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	7.5

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
Weaponized: 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 13 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

ghsa-q9j2-x62q-rv7w

What to do

AI-suggested

Until a fix is available, restrict access to the password change functionality to trusted users only and monitor for suspicious activity. Avoid allowing password changes without proper validation on the server side.

Description

Open Source Point of Sale version 3.4.1 contains a vulnerability in its password change endpoint that allows authenticated users to set their account password to an empty string. This occurs because the server does not validate the password fields properly, accepting empty values and returning a successful response. Setting an empty password effectively disables authentication for that account, potentially allowing unauthorized access to user or administrative accounts.

Impact

An attacker who is authenticated can exploit this vulnerability to set their password to an empty string, effectively disabling authentication on the account. This could lead to unauthorized access to user or administrative accounts, compromising account security and potentially allowing further malicious actions within the system.

Summary

The password change endpoint in Open Source Point of Sale 3.4.1 lacks server-side validation for the password and repeat_password parameters. When these parameters are omitted or left empty in a password change request by an authenticated user, the backend sets the account password to an empty string and returns success. This flaw can disable authentication, increasing the risk of unauthorized access to accounts, including administrative ones. The vulnerability is tracked as CVE-2025-63800 with a CVSS 3.1 base score of 7.5 (high severity).

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 adherence 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 13 Nov 2026, 20:08 UTC

WeaknessesCWE-521

Technical details

References

Community reviews

Related threats