CVE-2018-0695
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 · uneditedCross-site scripting vulnerability in User-friendly SVN (USVN) Version 1.0.7 and earlier allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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 scripting (XSS) vulnerability in User-friendly SVN (USVN) versions 1.0.7 and earlier. USVN is a web-based Subversion repository management tool. The flaw allows remote attackers to inject arbitrary web script or HTML through unspecified input vectors, likely due to insufficient input validation or output encoding in the web interface.
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.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Confirm USVN installationSearch for USVN files in common web directories (e.g., /var/www/, /usr/local/www/, or document roots like htdocs). Look for directories named 'usvn' containing USVN-specific files such as index.php, config.php, or the usvn/ subdirectory.Affected if USVN files are found in the web server's document root or a subdirectory.
-
Identify installed USVN versionLocate the version file or check the main USVN PHP files for a version constant. Common locations include usvn/version.php, usvn/include/defines.php, or the README file in the USVN installation directory. Open the file and read the version string.Affected if The version returned is 1.0.7 or any earlier version (e.g., 1.0.6, 1.0.5, 1.0.0).
-
Verify web interface is activeCheck if the USVN directory is accessible via the web server by accessing the application's URL (e.g., http://yourserver/usvn/). Confirm the login page or repository list loads successfully.Affected if The USVN web interface loads and is reachable over HTTP/HTTPS.
-
Check for unauthenticated input entry pointsIdentify USVN web forms that accept user input, such as login fields, search functions, repository creation forms, or user registration. Inspect the HTML source of these pages to locate form input elements.Affected if User input fields are present in the web interface without visible input validation indicators.
You are affected if USVN version 1.0.7 or earlier is installed and its web interface is accessible, as the XSS vulnerability exists in the web-facing input handling of these versions.
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 dataUpgrade to a patched version of USVN beyond 1.0.7. Until a patched version is available, implement output encoding for all user-supplied data displayed in the web interface and apply input validation on entry points.
- Consultation2.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0695 — 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-2018-0695 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