CVE-2022-33322
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 · uneditedCross-site scripting vulnerability in Mitsubishi Electric consumer electronics products (Air Conditioning, Wi-Fi Interface, Refrigerator, HEMS adapter, Remote control with Wi-Fi Interface, BATHROOM THERMO VENTILATOR, Rice cooker, Mitsubishi Electric HEMS control adapter, Energy Recovery Ventilator, Smart Switch and Air Purifier) allows a remote unauthenticated attacker to execute an malicious script on a user's browser to disclose information, etc. The wide range of models/versions of Mitsubishi Electric consumer electronics products are affected by this vulnerability. As for the affected product models/versions, see the Mitsubishi Electric's advisory which is listed in [References] section.
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 confidenceReflected cross-site scripting (XSS) vulnerability in the web interfaces of multiple Mitsubishi Electric consumer electronics products (air conditioners, Wi-Fi interfaces, refrigerators, HEMS adapters, ventilators, rice cookers, air purifiers, smart switches). An unauthenticated remote attacker can inject malicious JavaScript through unsanitized input parameters that executes in victim's browser, potentially leading to session hijacking or information disclosure.
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<= 35.00<= 35.00<= 35.00<= 35.00<= 35.00<= 80.00<= 80.00<= 35.00CVSS 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 your device modelLocate the product model number on the device label or documentation. Compare against the list of affected models: Mac 587if E, Mac 587if2 E, Mac 507if E, Mac 588if E, S Mac 002if, Ma Ew85s E, Ma Ew85s Uk, Mfz Gxt50/60/73vfkAffected if Your device model matches one of these affected models
-
Determine the installed firmware versionAccess the device web interface through a browser (typically http://[device-ip] or http://[device-hostname]) and navigate to the settings, system information, or about page. Alternatively, check the mobile app associated with the device if one is used for configuration.Affected if The firmware version displayed is <= 35.00 for Mac/S Mac models or <= 80.00 for Ma Ew85s models
-
Confirm the web interface is accessibleAttempt to reach the device web interface by entering its IP address or hostname in a web browser. Verify you receive a login or status page.Affected if The web interface loads and accepts input through URL parameters or form fields
-
Check for unsanitized input handlingReview HTTP requests and responses when interacting with the web interface. Look for any parameters that reflect user input back into the page without encoding (such as in search fields, configuration options, or device name settings).Affected if Input submitted through web interface parameters is reflected in the response without proper sanitization or HTML encoding
You are affected if your device model is one of the listed products, the firmware version is at or below the specified threshold, and the web interface is exposed and reflects user input without sanitization.
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 dataApply vendor-released firmware updates for affected products after consulting the Mitsubishi Electric security advisory for specific patched versions. Until patches are available, restrict network access to device web interfaces and monitor for suspicious requests.
- 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-2022-33322 — 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-2022-33322 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