CVE-2017-16950
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 · uneditedCross - site scripting (XSS) vulnerability in UrBackup Server before 2.1.20 allows remote attackers to inject arbitrary web script or HTML via the action parameter.
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 confidenceUrBackup Server before version 2.1.20 contains a reflected cross-site scripting (XSS) vulnerability in its web interface. The issue allows remote attackers to inject arbitrary JavaScript or HTML code through the 'action' parameter, which is not properly sanitized before being reflected back in the server's response.
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< 2.1.20CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 if UrBackup Server is installedCheck for running UrBackup Server processes (urbackupserver on Linux, or the UrBackup service on Windows) or look for installation directories such as /var/urbackup or C:\Program Files\UrBackup on Windows.Affected if UrBackup Server is found running on the system.
-
Determine the installed versionRun the version check command for UrBackup Server. On Linux, this is often available via 'urbackupsrv --version' or checking the package version. On Windows, right-click the service and view properties, or check the executable version in the installation folder.Affected if The version number returned is less than 2.1.20.
-
Confirm the web interface is enabledCheck the UrBackup Server configuration file (usually urbackupserver.cfg or settings in the database) for web interface settings. Look for entries enabling the web client or web server functionality, typically on port 55414 or 55415.Affected if The web interface is explicitly enabled in the configuration.
-
Verify web interface accessibilityAttempt to reach the web interface via browser or curl from a remote host using the configured port (commonly 55414). If accessible from non-localhost, the vulnerability is remotely exploitable.Affected if The web interface responds to HTTP requests from network locations.
The environment is affected if UrBackup Server version is below 2.1.20 AND the web interface is enabled and accessible.
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.
From vendor data2.1.20
Upgrade UrBackup Server to version 2.1.20 or later to obtain the patched version. If immediate upgrade is not feasible, consider web application firewall (WAF) rules to mitigate XSS attacks on the affected parameter.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16950 — 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-2017-16950 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