CVE-2022-0221· NVD / CVE Program· CNA schneider

A CWE-611: Improper Restriction of XML External Entity Reference vulnerability exists that could result in information disclosure when openi

A CWE-611: Improper Restriction of XML External Entity Reference vulnerability exists that could result in information disclosure when opening a malicious solution file provided by an attacker with SCADAPack Workbench. This could be exploited to pass data from local files to a remote system controlled by an attacker. Affected Product: SCADAPack Workbench (6.6.8a and prior)

MediumCVSS 5.5 · v3.1—No exploit No fix recorded

BDU:2023-00682

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Published: Apr 13, 2022
Updated: Jun 17, 2026
EPSS: 1.0% · 60th percentile
CWE: CWE-611

Follow this CVE

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.0%

CNA vs NVD score

NVD: 5.5
CNA · schneider: 5.5; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

Vendor	Product	CPE
schneider-electric	scadapack workbench	cpe:2.3:a:schneider-electric:scadapack_workbench

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

schneider-electric scadapack workbenchup to 6.6.8a inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (schneider). Independent of NVD's CPE analysis and usually ahead of it.

Schneider Electric SCADAPack Workbench
- 6.6.8a and later · before and prioraffected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).