CVE-2020-25070
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 · uneditedUSVN (aka User-friendly SVN) before 1.0.10 allows CSRF, related to the lack of the SameSite Strict feature.
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 confidenceUSVN (User-friendly SVN) before version 1.0.10 lacks the SameSite=Strict attribute on session cookies, allowing cross-site request forgery (CSRF) attacks. Attackers can exploit this by tricking authenticated users into visiting malicious pages that perform unintended actions against the USVN application.
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< 1.0.10CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 USVN versionCheck the version file or about page in your USVN installation. Common locations include VERSION file in the root directory, or the admin interface about page.Affected if The installed version is less than 1.0.10
-
Locate session cookie configurationFind the session configuration file in your USVN installation. This is typically in includes/ or config/ directories, often named Session.php or similar session handling files.Affected if The session cookie configuration does not include SameSite attribute
-
Inspect cookie headersLog into USVN and use browser developer tools (F12) or a proxy to capture the Set-Cookie header for the session cookie. Look for the SameSite=Strict attribute.Affected if The session cookie is missing the SameSite=Strict attribute or has SameSite=Lax or SameSite=None
-
Check CSRF protection mechanismsReview the application source code for CSRF token implementation. Look for forms that include CSRF tokens and verify the tokens are validated on submission.Affected if Forms lack CSRF tokens or tokens are not validated server-side
You are affected if your USVN version is below 1.0.10 AND your session cookies lack the SameSite=Strict attribute, making authenticated users vulnerable to cross-site request forgery attacks.
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 data1.0.10
Upgrade to USVN 1.0.10 or later which implements SameSite=Strict cookie attributes. As a temporary workaround, ensure users are warned about clicking untrusted links while authenticated.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25070 — 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-25070 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