CVE-2025-34392

Barracuda Rmm remote code execution

9.8 CRITICALPublic exploitEPSS 24.7%

Published10 Dec 2025

Description

Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not verify the URL defined in an attacker-controlled WSDL that is later loaded by the application. This can lead to arbitrary file write and remote code execution via webshell upload.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Barracuda Rmm< 2025.1.1

Remediation

Fixed in

Barracuda Rmm≥ 2025.1.1

References

https://download.mw-rmm.barracudamsp.com/PDF/2025.1.1/RN_BRMM_2025.1.1_EN.pdfRelease Notes
https://labs.watchtowr.com/soapwn-pwning-net-framework-applications-through-http-client-proxies-and-wsdl/ExploitThird Party Advisory
https://www.barracuda.com/products/msp/network-protection/rmmProduct
https://www.vulncheck.com/advisories/barracuda-rmm-service-center-absolute-path-traversal-rceThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-34392 being actively exploited?

CVE-2025-34392 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 24.7%.

How severe is CVE-2025-34392?

CVE-2025-34392 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 24.7% probability of exploitation.

Which products are affected by CVE-2025-34392?

Affected products include Barracuda Rmm.

How do I fix CVE-2025-34392?

Upgrade affected software to a fixed version, for example Barracuda Rmm 2025.1.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-34392 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.