CVE-2020-24570
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.1. There is a CSRF issue (with resultant SSRF) in the com_mb24proxy module, allowing attackers to steal session information from logged-in users with a crafted link.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the com_mb24proxy module of mymbCONNECT24 and mbCONNECT24 allows attackers to craft malicious links that trigger unauthorized server-side requests (SSRF), enabling session hijacking and theft of session information from authenticated users.
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.1<= 2.6.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 mbCONNECT24 installationLocate the mbCONNECT24 or mymbCONNECT24 installation directory, typically found in the web server's document root under /mbconnect24 or /mymbconnect24Affected if The product is installed and accessible via web browser
-
Identify installed versionAccess the admin interface or check version file (often version.php, changelog.txt, or admin/config.php) to determine the exact version numberAffected if Version is 2.6.1 or lower (vulnerable range)
-
Check com_mb24proxy module presenceVerify the com_mb24proxy module exists in the installation - look for proxy-related PHP files or modules within the components directoryAffected if The com_mb24proxy module is present and loaded by the application
-
Determine if proxy functionality is enabledCheck the administrative settings or configuration panel for the proxy module to see if it is active or accessible to usersAffected if The proxy module is enabled and accessible without additional authentication barriers beyond session login
-
Inspect session handling for CSRF tokensReview the proxy module source code or proxy request handling logic for absence of anti-CSRF token validation in form submissions or URL-based requestsAffected if No CSRF token validation is implemented in the com_mb24proxy module requests
You are affected if mbCONNECT24 or mymbCONNECT24 version 2.6.1 or lower is installed with the com_ms24proxy module enabled and accessible, and the proxy lacks CSRF token protection.
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 and validate request origin/referer headers in the com_mb24proxy module to prevent forged requests; consider adding SameSite cookie attributes and requiring re-authentication for sensitive proxy operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24570 — 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-24570 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