VulnerabilityPublished 9 Mar 2026

CVE-2025-41772: MBS UBR-01 Mk II · Use of GET Request Method With Sensitive Query Strings

Affects MBS UBR-01 Mk IISource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 6.0.1.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% 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: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 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 30 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

Immediately restrict access to the wwwupdate.cgi endpoint by implementing network-level controls such as firewall rules or VPN-only access to management interfaces.
Disable or limit the use of HTTP GET requests for sensitive operations; if possible, configure the device or update firmware to use POST requests or other secure methods that do not expose tokens in URLs.
Implement strict logging and monitoring of access to the vulnerable endpoint to detect suspicious activity or token harvesting attempts.
Rotate session tokens frequently and invalidate tokens exposed in URLs to minimize the window of exploitation.
If possible, isolate affected devices within segmented network zones with limited exposure to untrusted networks.
Engage with the vendor (MBS) to obtain patches or firmware updates addressing this vulnerability.
Educate administrators on the risks of exposing session tokens in URLs and enforce secure session management practices.
Consider deploying web application firewalls (WAFs) or intrusion detection systems (IDS) with custom rules to detect and block attempts to exploit this vulnerability.

Description

An unauthenticated remote attacker can obtain valid session tokens because they are exposed in plaintext within the URL parameters of the wwwupdate.cgi endpoint in UBR.

Impact

The primary impact of this vulnerability is the compromise of confidentiality through session token leakage. Attackers can obtain valid session tokens without authentication, enabling unauthorized access to the affected device's management interfaces or services. This can lead to unauthorized configuration changes, data exposure, or further lateral movement within a network. While integrity and availability are not directly impacted, the unauthorized access enabled by token theft can indirectly lead to malicious modifications or service disruptions. Organizations deploying MBS UBR-01 Mk II devices in critical infrastructure, telecommunications, or enterprise networks face increased risk of targeted attacks. The ease of exploitation and network accessibility mean that attackers can remotely compromise devices without user interaction, increasing the likelihood of automated scanning and exploitation attempts once the vulnerability becomes widely known. The lack of patches further elevates risk, necessitating immediate mitigation efforts.

CWE-598Use of HTTP Request With Sensitive Query String (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.
Implementation
When sending sensitive information, only include it in the request body or request headers instead of the query string. This may require avoiding use of GET requests.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V3.1.1 (opens in a new tab)
V13.1.3 (opens in a new tab)
V8.3.4 (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:47 UTC

WeaknessesCWE-598

Technical details

References

Community reviews

Related threats