CVE-2020-35569
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 · uneditedAn issue was discovered in MB CONNECT LINE mymbCONNECT24 and mbCONNECT24 through 2.6.2. There is a self XSS issue with a crafted cookie in the login page.
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 mbCONNECT24 login page reflects unsanitized cookie values in the page content, allowing an attacker to craft a malicious cookie containing JavaScript that executes when a victim visits the login page. This self-XSS requires the user to have the crafted cookie set in their browser, typically achieved through social engineering or man-in-the-middle attacks.
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<= 2.6.2<= 2.6.2CVSS 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 the mbCONNECT24 product variantDetermine whether the installation is Mbconnect24 or Mymbconnect24 by checking the product name shown in the web interface or system documentation.Affected if The product is either Mbconnect24 or Mymbconnect24.
-
Locate the installed version numberAccess the admin interface or check system files that contain version information for the mbCONNECT24 installation.Affected if The installed version is 2.6.2 or lower.
-
Inspect login page for cookie reflectionVisit the login page and view the page source (right-click > View Page Source). Search for cookie value patterns or parameter names that may be reflected in the HTML without encoding.Affected if Cookie values or parameters appear in the HTML output without proper HTML encoding (e.g., unescaped <, >, or quote characters).
-
Test cookie value injectionManually set a test cookie with a benign value containing special characters (such as <script>alert(1)</script>) and navigate to the login page. Examine whether these characters render as plain text or execute as code.Affected if The special characters render unescaped or the browser executes the test payload.
A user is affected if they are running Mbconnect24 or Mymbconnect24 version 2.6.2 or lower and the login page reflects cookie values without HTML encoding.
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 output encoding/sanitization on all cookie values before rendering them in HTML context. Additionally, set the HttpOnly flag on sensitive cookies to prevent JavaScript access, and consider Content-Security-Policy headers to mitigate XSS execution.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35569 — 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-35569 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