dbcve.org
Wiser Smart Eer21000 FirmwareOperating system · Schneider Electric

CVE-2022-30238

HIGH · 8.8 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to after 4.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A CWE-287: Improper Authentication vulnerability exists that could allow an attacker to take over the admin account when an attacker hijacks a session. Affected Products: Wiser Smart, EER21000 & EER21001 (V4.5 and prior)

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 confidence

This is a session hijacking vulnerability (CWE-287 Improper Authentication) in Wiser Smart EER21000 and EER21001 devices running firmware V4.5 and prior. An attacker who successfully hijacks a valid admin session can take over the admin account, bypassing proper authentication controls.

MitigationUpgrade affected devices to firmware newer than V4.5. Until patched, implement network segmentation and monitor for anomalous session behavior to reduce the risk of session hijacking attempts.

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
Wiser Smart Eer21000 FirmwareOperating system
Affected:<= 4.5
Wiser Smart Eer21001 FirmwareOperating system
Affected:<= 4.5

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device admin interface or check the device label to confirm the exact model number (EER21000 or EER21001). Compare against the affected product list.
    Affected if The device is a Wiser Smart EER21000 or EER21001 model.
  2. Determine the installed firmware version
    Log into the device admin panel and navigate to the firmware or system information section. Note the firmware version number displayed.
    Affected if The firmware version is V4.5 or any version prior to V4.5.
  3. Verify admin session management configuration
    Access the admin session settings or user management area in the device web interface. Inspect whether session tokens are properly validated and whether session fixation protections are enabled.
    Affected if Session management allows session hijacking or does not properly validate admin session tokens.
  4. Check for active admin sessions
    Review the admin session list or logged-in users panel in the device interface. Note any unexpected or unauthorized admin sessions.
    Affected if Multiple admin sessions are active simultaneously or sessions from unexpected IP addresses are detected.
  5. Review session activity logs
    Examine the device logs or event history for authentication events, particularly successful logins followed by rapid privilege escalation or configuration changes.
    Affected if Logs show admin session activity that was not initiated by the legitimate administrator.

A user is affected if they have a Wiser Smart EER21000 or EER21001 device running firmware V4.5 or earlier, where admin sessions can be hijacked due to improper authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.5
Interim mitigation

Upgrade affected devices to firmware newer than V4.5. Until patched, implement network segmentation and monitor for anomalous session behavior to reduce the risk of session hijacking attempts.

Recommended fix Moderate confidence

Any firmware version higher than 4.5 (contact Schneider Electric for the specific fixed release)

  1. 1. Identify the current firmware version of the Wiser Smart EER21000 or EER21001 device
  2. 2. Access the device management interface or use the appropriate firmware update mechanism provided by Schneider Electric
  3. 3. Download the latest firmware version from the official Schneider Electric support website (www.se.com) for your specific device model
  4. 4. Follow the manufacturer's firmware update instructions carefully to apply the upgrade
  5. 5. Verify the firmware upgrade was successful and confirm the device is running a version higher than 4.5
  6. 6. After upgrading, change the admin password as a security best practice
Caveat Review Schneider Electric release notes for any configuration or feature changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wiser Smart Eer21000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30238 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30238 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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