CVE-2025-34521
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 · uneditedA reflected cross-site scripting (XSS) vulnerability exists in the web interface of the Arcserve Unified Data Protection (UDP), where unsanitized user input is improperly reflected in HTTP responses. This flaw allows remote attackers with low privileges to craft malicious links that, when visited by another user, execute arbitrary JavaScript in the victim’s browser. Successful exploitation may lead to session hijacking, credential theft, or other client-side impacts. The vulnerability requires user interaction and occurs within a shared browser context. This vulnerability affects all UDP versions prior to 10.2. UDP 10.2 includes the necessary patches and requires no action. Versions 8.0 through 10.1 are supported and require either patch application or upgrade to 10.2. Versions 7.x and earlier are unsupported or out of maintenance and must be upgraded to 10.2 to remediate the issue.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the Arcserve UDP web interface where unsanitized user input is improperly reflected in HTTP responses. Attackers with low privileges can craft malicious links that execute arbitrary JavaScript in victim browsers, potentially leading to session hijacking or credential theft.
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< 7.0>= 8.0, < 10.2= 7.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Arcserve UDP versionOpen Windows Control Panel > Programs and Features, locate 'Arcserve Unified Data Protection' or 'Arcserve UDP' in the list, and note the Version columnAffected if The version shown is less than 10.2 (including versions < 7.0, version 7.0, or versions 8.0-10.1)
-
Check Arcserve UDP web interface accessibilityOpen a web browser and attempt to access the UDP web console by navigating to https://localhost:8015 or the configured hostname/port for your Arcserve UDP installationAffected if The web interface loads and is reachable on the network
-
Verify web interface is enabledOn the Arcserve UDP server, open Arcserve UDP Configuration or check Windows Services for 'Arcserve UDP Web Server' or similar service; confirm it is runningAffected if The web server service is running and accepting connections
-
Confirm version via product interfaceIf the web console is accessible, log in and navigate to Help > About or Settings > System Information to view the exact product versionAffected if The reported version is below 10.2
A user is affected if Arcserve UDP version is installed and the web interface is enabled, with the version being less than 10.2 (including versions < 7.0, 7.0 exactly, or 8.0-10.1)
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.010.2
Upgrade to UDP version 10.2 or apply the available patch to versions 8.0-10.1 to implement proper input sanitization and output encoding.
Arcserve UDP 10.2
- 1. Review the Arcserve UDP 10.2 release notes and upgrade documentation at support.arcserve.com for complete upgrade instructions
- 2. Create a complete backup of the current UDP configuration and database
- 3. Schedule a maintenance window as the upgrade will require system downtime
- 4. Download the UDP 10.2 installation package from the official Arcserve download portal
- 5. Stop all UDP services on the server before proceeding with the upgrade
- 6. Run the UDP 10.2 installer and follow the on-screen upgrade wizard
- 7. After installation completes, verify all services start successfully
- 8. Log in to the UDP web interface and confirm version 10.2 is displayed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34521 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34521 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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