CVE-2020-35564
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 an outdated and unused component allowing for malicious user input of active code.
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 confidenceAn outdated and unused component in mymbCONNECT24 and mbCONNECT24 (versions through 2.6.2) processes malicious user input as active code, indicating a code injection or cross-site scripting (XSS) vulnerability where user-supplied data is not properly sanitized before execution.
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
- 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 installed version of mbCONNECT24 or mymbCONNECT24Check the application's version information - typically found in the admin panel, about section, or in the application configuration files. Common locations include the web interface footer, a /version endpoint, or configuration XML/JSON files in the installation directory.Affected if The installed version is 2.6.2 or lower.
-
Locate unused or outdated componentsInspect the application installation directory for legacy or deprecated components. Check for old scripts, modules, or endpoints that may no longer be actively maintained. Look for folders named 'old', 'deprecated', 'legacy', or unused plugin directories.Affected if Unused or outdated components from older versions are still present in the installation.
-
Verify if the vulnerable component is still enabledReview the application's configuration files and server settings (such as Apache/nginx config, application config XML, or web.xml) to determine if the outdated component is actively loaded or accessible.Affected if The outdated component is still enabled and accessible via web requests.
-
Check user input handling in the applicationTest the application by submitting special characters (< > script alert) in input fields, especially in areas related to the unused component. Review application logs for any XSS filter warnings or errors.Affected if User-supplied input in web forms or parameters is rendered back without sanitization or encoding.
A user is affected if the installed mbCONNECT24 or mymbCONNECT24 version is 2.6.2 or lower AND the unused/outdated component is still present and enabled in the application.
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 dataLocate and remove or disable the unused/outdated component from the application; if a patched version is available, upgrade to the fixed release.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35564 — 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-35564 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