VulnerabilityPublished 9 Mar 2026

CVE-2025-41763: MBS UBR-01 Mk II · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects MBS UBR-01 Mk IISource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 6.0.1.0 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.0.1.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 9 Mar 2026
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 29 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.
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.

What to do

Upgrade UBR-01 Mk II and UBR-02 and UBR-LON to 6.0.1.0.

Affected software

Product	Affected	Fixed in
MBSUBR-01 Mk II	Affected <6.0.1.0	Fixed in 6.0.1.0
MBSUBR-02	Affected <6.0.1.0	Fixed in 6.0.1.0
MBSUBR-LON	Affected <6.0.1.0	Fixed in 6.0.1.0

AI-suggested

Restrict access to the wwwdnload.cgi endpoint by implementing network segmentation and firewall rules to limit access only to trusted administrative hosts.
Employ strong authentication and authorization controls to ensure only authorized personnel can access administrative interfaces.
Monitor and log all access attempts to the wwwdnload.cgi endpoint, and set up alerts for unusual or unauthorized download activities.
If possible, disable or remove the wwwdnload.cgi endpoint if it is not essential for operations.
Regularly audit device configurations and backup files to detect any unauthorized access or changes.
7. Consider deploying intrusion detection/prevention systems (IDS/IPS) to detect exploitation attempts targeting this CGI endpoint. 8. Educate network and security teams about this vulnerability to ensure rapid response to any suspicious activity. 9. Implement encryption and secure storage for backups and certificate files to minimize the impact if accessed. 10. Conduct penetration testing and vulnerability assessments focused on administrative interfaces to identify similar weaknesses.

Description

A low‑privileged remote attacker can directly interact with the wwwdnload.cgi endpoint to download any resource available to administrators, including system backups and certificate request files.

Impact

The primary impact of CVE-2025-41763 is the unauthorized disclosure of sensitive system information. Attackers exploiting this vulnerability can obtain system backups and certificate request files, which may contain sensitive configuration data, cryptographic keys, and credentials. This exposure can lead to significant confidentiality breaches, enabling attackers to conduct further attacks such as impersonation, man-in-the-middle attacks, or unauthorized system access. While the vulnerability does not directly affect system integrity or availability, the information gained can be leveraged to compromise these aspects indirectly. Organizations relying on MBS UBR-01 Mk II devices, especially in critical infrastructure, telecommunications, or enterprise environments, face increased risk of targeted attacks. The ease of exploitation (low privileges, no user interaction) increases the likelihood of exploitation attempts. The absence of known exploits in the wild currently limits immediate widespread impact, but the vulnerability remains a significant risk if weaponized. Data confidentiality loss could also lead to regulatory compliance issues and reputational damage.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

mbs-solutions.de/mbs-2025-0001 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Mar 2026, 09:42 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats