CVE-2021-45878
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 · uneditedMultiple versions of GARO Wallbox GLB/GTB/GTC are affected by incorrect access control. Lack of access control on the web manger pages allows any user to view and modify information.
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 confidenceThe GARO Wallbox GLB/GTB/GTC electric vehicle charging stations have incorrect access control in their web manager interface. The lack of authentication and authorization enforcement on web pages allows any user (unauthenticated or unauthorized) to access sensitive management pages and view or modify system information and configurations.
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<= 185<= 185<= 185CVSS 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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 the GARO Wallbox modelLocate the device label or use network discovery to confirm the model is GARO Wallbox GLB, GTB, or GTCAffected if The device is not a GARO Wallbox GLB, GTB, or GTC model
-
Check the installed firmware versionAccess the device web interface or use the manufacturer's diagnostic tool to retrieve the firmware version numberAffected if Firmware version is 185 or lower (any version <= 185)
-
Verify the web manager interface is network-accessibleAttempt to access the device IP address on HTTP/HTTPS ports (typically 80/443) from a network-connected hostAffected if The web interface is reachable over the network
-
Test for unauthenticated access to management pagesNavigate to common management paths such as /settings, /config, /admin, or /status without providing any login credentialsAffected if Management or configuration pages load without requiring any authentication or login
-
Confirm sensitive data exposureInspect the loaded pages for system information, user credentials, configuration data, or charging session logs without being logged inAffected if Sensitive system information or configuration options are visible without authentication
You are affected if you have a GARO Wallbox GLB, GTB, or GTC device running firmware version 185 or lower with an accessible web interface that allows unauthenticated access to management pages.
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 proper authentication and authorization controls on all web manager pages. Apply vendor-supplied firmware updates that address the access control vulnerabilities, and restrict network access to the device management interfaces.
- 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-2021-45878 — 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-2021-45878 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