T0510: Missing Authentication for Critical Functionality
CVE-2025-6763 is a high-severity missing authentication for critical functionality vulnerability in T0510 from Comet System, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected T0510 versions: 1.60. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.38% chance of exploitation within 30 days, higher than 72% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of T0510 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 |
|---|---|---|---|
| Comet System | T0510 | 1.60 | Not stated |
| Comet System | T3510 | 1.60 | Not stated |
| Comet System | T3511 | 1.60 | Not stated |
| Comet System | T4511 | 1.60 | Not stated |
| Comet System | T6640 | 1.60 | Not stated |
| Comet System | T7511 | 1.60 | Not stated |
| Comet System | T7611 | 1.60 | Not stated |
| Comet System | P8510 | 1.60 | Not stated |
| Comet System | P8552 | 1.60 | Not stated |
| Comet System | H3531 | 1.60 | Not stated |
| Cometsystem | T7611 Firmware | 1-5-7-5.1252 | Not stated |
| Cometsystem | T4511 Firmware | 1-5-7-5.1252 | Not stated |
| Cometsystem | T0510 Firmware | 1-5-7-5.1252 | Not stated |
| Cometsystem | T6640 Firmware | 1-5-7-5.1252 | Not stated |
| Cometsystem | T3510 Firmware | 1-5-7-5.1252 | Not stated |
| Cometsystem | T7511 Firmware | 1-5-7-5.1251 | Not stated |
| Cometsystem | T3511 Firmware | 1-5-7-2.1151 | Not stated |
| Cometsystem | P8510 Firmware | 4-5-8-0.3488 | Not stated |
| Cometsystem | P8552 Firmware | 4-5-8-1.3502 | Not stated |
| Cometsystem | H3531 Firmware | 9-5-0-1.1327 | Not stated |
Version data comes from the organisation that assigned the CVE. 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
- HighSuccess depends on conditions outside the attacker's control.
- 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
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (vuldb.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.2 | High | CNA (vuldb.com) |
| CVSS 3.1 | 8.1 | High | CNA (vuldb.com) |
| CVSS 2.0 | 7.6 | High | CNA (vuldb.com) |
Official description
A vulnerability was found in Comet System T0510, T3510, T3511, T4511, T6640, T7511, T7611, P8510, P8552 and H3531 1.60. Affected by this issue is some unknown functionality of the file /setupA.cfg of the component Web-based Management Interface. Performing manipulation results in missing authentication. The attack may be initiated remotely. A high degree of complexity is needed for the attack. The exploitation is known to be difficult. The exploit has been made public and could be used. There are still doubts about whether this vulnerability truly exists. The vendor explains, that "[d]evices described at CVE are not intended to be exposed into internet and proper security of devices is to end-users."
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- vuldb.com/?id.314074Third Party Advisory, VDB Entry
- vuldb.com/?submit.599848Third Party Advisory, VDB Entry
Technical write-ups (may include proof of concept)
- github.com/zeke2997/CVE_request_comet_systemExploit, Third Party Advisory
- github.com/zeke2997/CVE_request_comet_system#pocExploit, Third Party Advisory
Other references
- vuldb.com/?ctiid.314074Permissions Required, VDB Entry
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 8.2 High severity
- 9.6 Critical severity
- 10.0 Critical severity
Spotted an error? Tell us.