CVE-2019-25046
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 · uneditedThe Web Client in Cerberus FTP Server Enterprise before 10.0.19 and 11.x before 11.0.4 allows XSS via an SVG document.
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 confidenceThe Cerberus FTP Server Enterprise web client allows stored Cross-Site Scripting (XSS) through malicious SVG document uploads. SVG files can contain embedded JavaScript that executes when viewed in the browser, allowing attackers to steal session cookies or perform actions as the victim user.
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< 10.0.19>= 11.0.0, < 11.0.4CVSS 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.1/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.
-
Verify Cerberus FTP Server web client is enabledIn the Cerberus FTP Server admin console, go to Interface > Web Server and check if the web server is running and enabled.Affected if The web client must be enabled for the XSS vulnerability to be exploitable.
-
Confirm installed Cerberus FTP Server versionIn the admin console, go to Help > About or check the version displayed on the main interface. Compare this to the affected ranges: version < 10.0.19 or >= 11.0.0 and < 11.0.4.Affected if The installed version falls within < 10.0.19 or >= 11.0.0 and < 11.0.4.
-
Check if web file upload is accessible to non-admin usersIn the admin console, go to Users > [select user] > Permissions and verify if the user has Web File Upload permission enabled, or check the web client access settings for general upload functionality.Affected if Web file upload permissions are granted to users who can upload SVG files to the server.
-
Inspect uploaded SVG files in web client directoriesIf web uploads are enabled, examine any SVG files in user-accessible web upload directories for suspicious script tags, embedded JavaScript, or onload/onerror attributes.
A user is affected if the Cerberus FTP Server web client is enabled, the installed version is vulnerable (< 10.0.19 or >= 11.0.0 to < 11.0.4), and web file upload functionality is accessible to users who could upload malicious SVG files.
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 data10.0.1911.0.4
Upgrade to Cerberus FTP Server Enterprise version 10.0.19 or 11.0.4 or later, which includes proper sanitization of uploaded SVG files. Until patched, disable the web client or restrict upload functionality to trusted users.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25046 — 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-2019-25046 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