CVE-2020-15789
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 vulnerability has been identified in Polarion Subversion Webclient (All versions). The web interface could allow a Cross-Site Request Forgery (CSRF) attack if an unsuspecting user is tricked into accessing a malicious link. Successful exploitation requires user interaction by a legitimate user, who must be authenticated to the web interface. A successful attack could allow an attacker to trigger actions via the web interface that the legitimate user is allowed to perform. This could allow the attacker to read or modify contents of the web application.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in Polarion Subversion Webclient allows attackers to trick authenticated users into unknowingly executing unwanted actions via malicious links. Since the web application lacks proper anti-CSRF token validation, attackers can perform operations (read/modify) that the legitimate authenticated user is authorized to perform.
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 dataall versionsCVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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.
-
Confirm Polarion Subversion Webclient is accessibleCheck if the Polarion web interface is reachable at your deployment URL (typically under /polarion or similar path). Look for the Subversion Webclient module.Affected if The product is deployed and accessible on the network.
-
Identify if authentication is requiredAttempt to access the Subversion Webclient without credentials. Observe whether the application requires login or returns an authenticated session.Affected if The application requires user authentication before access.
-
Inspect form submissions for CSRF tokensLog into the Subversion Webclient and examine HTML forms that perform state-changing actions (POST/PUT/DELETE requests). Look for hidden input fields containing tokens or anti-CSRF parameters in the form markup.Affected if Forms performing write operations lack anti-CSRF token fields in the HTML.
-
Check API requests for token validationUse browser developer tools to intercept requests for state-changing operations. Verify whether request headers or parameters include CSRF tokens that the server validates.Affected if State-changing API requests do not include CSRF tokens in headers or parameters.
-
Verify session cookie SameSite attributeInspect session cookies using browser developer tools or by examining Set-Cookie headers. Check if the SameSite attribute is set to 'Strict' or 'Lax' for session cookies.Affected if Session cookies are missing the SameSite attribute or have it set to 'None' without Secure flag.
If Polarion Subversion Webclient is running and accessible, and any of the checks 3-5 reveal missing CSRF token validation or improper SameSite cookie configuration, the environment is affected by this CVE.
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 dataImplement anti-CSRF tokens on all state-changing operations (POST/PUT/DELETE) and validate these tokens server-side for every request. Additionally, configure the SameSite attribute on session cookies.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15789 — 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-2020-15789 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