dbcve.org
RmmApplication · Barracuda

CVE-2025-34392

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 2025.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Barracuda RMM Service Center fails to validate URLs within attacker-controlled WSDL files before loading them. An attacker can specify a malicious URL in a WSDL that causes the application to write arbitrary files to the filesystem, enabling webshell upload and remote code execution.

MitigationUpgrade Barracuda RMM to version 2025.1.1 or later to patch the WSDL URL validation vulnerability. If immediate patching is not possible, restrict access to the Service Center interface and monitor for suspicious WSDL uploads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RmmApplication
Affected:< 2025.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Barracuda RMM installation
    Check for Barracuda RMM service by looking for the 'barracuda' or 'BRMM' process in Task Manager (Windows) or running 'ps aux | grep -i barracuda' (Linux). Also check for installation directories such as C:\Program Files\Barracuda\ or /opt/barracuda/.
    Affected if Barracuda RMM is not installed on the system
  2. Determine installed version
    On Windows, check the installed version via Control Panel > Programs and Features > Barracuda RMM, or check the version file typically located in the installation directory. On Linux, run 'rpm -q barracuda-rmm' or 'dpkg -l | grep barracuda' if installed via package manager.
    Affected if The installed version is before 2025.1.1 (e.g., 2024.x, 2023.x, etc.)
  3. Verify Service Center component status
    Access the Barracuda RMM web interface and navigate to the Service Center module. Check if the Service Center is enabled and accessible via its administrative portal.
    Affected if Service Center is enabled and accessible without authentication restrictions
  4. Inspect for unauthorized WSDL files
    Search the Barracuda RMM installation directory and webroot for unexpected .wsdl or .xml files, especially in upload directories or temporary folders. Use file system monitoring to identify recently created WSDL files.
    Affected if Unknown or attacker-created WSDL files are present in the system
  5. Check for webshell indicators
    Review web server access logs and application logs for unusual POST requests to .asp, .aspx, .jsp, or .php files in non-standard locations. Look for suspicious outbound network connections from the server.
    Affected if Unrecognized webshell files exist or suspicious outbound connections are observed

The environment is affected if Barracuda RMM with Service Center version before 2025.1.1 is installed and the Service Center component is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.1.1 or later
Fixed in 2025.1.1
Interim mitigation

Upgrade Barracuda RMM to version 2025.1.1 or later to patch the WSDL URL validation vulnerability. If immediate patching is not possible, restrict access to the Service Center interface and monitor for suspicious WSDL uploads.

Recommended fix High confidence

2025.1.1

  1. 1. Identify the current version of Barracuda RMM by checking the Service Center or RMM dashboard.
  2. 2. If the current version is earlier than 2025.1.1, obtain the version 2025.1.1 or later from the official Barracuda MSP download portal (download.mw-rmm.barracudamsp.com) or your Barracuda support channel.
  3. 3. Apply the upgrade following Barracuda's standard RMM upgrade procedure, ensuring proper backups are taken beforehand.
  4. 4. After upgrade, verify the RMM version shows 2025.1.1 or later in the Service Center.
  5. 5. Confirm the vulnerability is remediated by validating that WSDL URL validation is now enforced and arbitrary file writes are no longer possible.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rmm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34392 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34392 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data