CVE-2021-35243
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 HTTP PUT and DELETE methods were enabled in the Web Help Desk web server (12.7.7 and earlier), allowing users to execute dangerous HTTP requests. The HTTP PUT method is normally used to upload data that is saved on the server with a user-supplied URL. While the DELETE method requests that the origin server removes the association between the target resource and its current functionality. Improper use of these methods may lead to a loss of integrity.
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 Web Help Desk (12.7.7 and earlier) web server had HTTP PUT and DELETE methods enabled, which should typically be disabled. PUT allows attackers to upload arbitrary files to the server while DELETE can remove resources, leading to potential integrity compromise.
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<= 12.7.7CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Web Help Desk installationLocate the SolarWinds Web Help Desk installation directory and check the version information file, typically found in the application directory or via the application's About/Help sectionAffected if Version is 12.7.7 or lower (or if the version cannot be determined but the product is installed)
-
Verify HTTP methods are enabledSend HTTP OPTIONS request to the Web Help Desk server or inspect the web server (IIS, Apache, or embedded server) configuration to list allowed HTTP methodsAffected if HTTP PUT method is listed as allowed/enabled
-
Verify DELETE method is enabledInspect the same web server configuration used in the previous step to confirm DELETE method is also enabledAffected if HTTP DELETE method is listed as allowed/enabled
If Web Help Desk version 12.7.7 or lower is installed AND both HTTP PUT and DELETE methods are enabled on the server, the environment is affected by this vulnerability.
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 · scopedDisable HTTP PUT and DELETE methods in the web server (e.g., IIS, Apache, or embedded server) configuration to prevent unauthorized file uploads or resource deletion.
Web Help Desk version newer than 12.7.7 (contact SolarWinds support for exact fixed release)
- Contact SolarWinds support or visit the official SolarWinds support portal to obtain the latest stable version of Web Help Desk that addresses CVE-2021-35243
- Review the upgrade documentation provided by SolarWinds for Web Help Desk
- Plan the upgrade process, including backing up the current Web Help Desk configuration and database
- Schedule a maintenance window to perform the upgrade
- Execute the upgrade following the official SolarWinds upgrade procedures
- Verify that the HTTP PUT and DELETE methods are now disabled or properly restricted after the upgrade
- Test the Web Help Desk functionality to ensure normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35243 — 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-2021-35243 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