CVE-2022-36967
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 · uneditedIn Progress WS_FTP Server prior to version 8.7.3, multiple reflected cross-site scripting (XSS) vulnerabilities exist in the administrative web interface. It is possible for a remote attacker to inject arbitrary JavaScript into a WS_FTP administrator's web session. This would allow the attacker to execute code within the context of the victim's browser.
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 confidenceReflected XSS vulnerability in Progress WS_FTP Server administrative web interface allows remote attackers to inject arbitrary JavaScript into an administrator's session by tricking the victim into visiting a crafted URL, enabling code execution within the victim's browser context.
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< 8.7.3CVSS 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.
-
Identify if WS_FTP Server is installedCheck for WS_FTP Server installation by looking in Windows Programs and Features, or check for the service named 'WS_FTP Server' in Services console (services.msc)Affected if WS_FTP Server is found installed on the system
-
Determine installed WS_FTP Server versionOpen Windows Registry and navigate to HKLM\SOFTWARE\Ipswitch\WS_FTP Server\ or check the version property of the installed executable (typically in C:\Program Files\Ipswitch\WS_FTP Server\)Affected if The installed version is lower than 8.7.3
-
Verify the administrative web interface is enabledCheck if the WS_FTP Server web administration service is running by looking for the WS_FTP Server Administrative Service in Windows Services, or test connectivity to the admin web ports (default 8080 or 443)Affected if The administrative web interface service is running and accessible
-
Confirm web interface is network-accessibleAttempt to access the WS_FTP admin web interface from a browser using the server's hostname or IP on the configured port (such as http://hostname:8080 or https://hostname:443)Affected if The admin web interface responds to HTTP/HTTPS requests, indicating it is network-reachable
The environment is affected if WS_FTP Server is installed with a version lower than 8.7.3 and the administrative web interface is running 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.
dbcve · scoped8.7.3
Upgrade WS_FTP Server to version 8.7.3 or later to patch the reflected XSS vulnerabilities in the administrative web interface.
8.7.3
- 1. Identify current WS_FTP Server version by accessing the administrative web interface or checking the installed software.
- 2. If version is below 8.7.3, obtain the fixed version 8.7.3 from Progress official download channels (community.progress.com or www.progress.com).
- 3. Before upgrading, backup the current WS_FTP Server configuration and data.
- 4. Apply the version 8.7.3 upgrade following Progress standard upgrade procedures.
- 5. After upgrade, verify the administrative web interface is accessible and functioning normally.
- 6. Confirm the XSS vulnerability is remediated by reviewing release notes or verifying the fixed version is installed.
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2022-36967 — 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-2022-36967 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