CVE-2025-41759: Use of wildcard (“*” or “all”) in Block list

Published Mar 9, 2026
·
Updated

An administrator may attempt to block all networks by specifying "\" or "all" as the network identifier. However, these values are not supported and do not trigger any validation error. Instead, they are silently interpreted as network 0 which results in no networks being blocked at all.

Affected Software

4 affected components
All of the following
Mbs-solutions Universal Bacnet Router Firmware<6.0.1.0
Any of the following
Mbs-solutions Ubr-01 Mk Ii
Mbs-solutions Ubr-02
Mbs-solutions Ubr-lon

Event History

Mar 9, 2026
CVE Published
via MITRE·08:16 AM
Data Sourced
via MITRE·08:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-41759?

CVE-2025-41759 is classified as a high severity vulnerability due to the potential for unauthorized network access.

2

How do I fix CVE-2025-41759?

To fix CVE-2025-41759, ensure that no wildcard characters like '*' or 'all' are used in the block list and perform a proper validation of network identifiers.

3

What system components are affected by CVE-2025-41759?

CVE-2025-41759 affects the Mbs-solutions Universal Bacnet Router Firmware version prior to 6.0.1.0.

4

What can happen if CVE-2025-41759 is exploited?

Exploitation of CVE-2025-41759 can allow unauthorized devices to communicate with the network, undermining security measures.

5

Who is responsible for the CVE-2025-41759 vulnerability?

The CVE-2025-41759 vulnerability is the responsibility of Mbs-solutions, the vendor of the affected firmware.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203