dbcve.org
Accusine Pcsp Pfvp FirmwareOperating system · Schneider Electric

CVE-2021-22793

HIGH · 7.2 CVSS v3.1 Published 2021-09-02
Fix available
A fix is available. Upgrade to 001.006.007 / 002.002.004 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click Patch available

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-200: Exposure of Sensitive Information to an Unauthorized Actor vulnerability exist in AccuSine PCS+ / PFV+ (Versions prior to V1.6.7) and AccuSine PCSn (Versions prior to V2.2.4) that could allow an authenticated attacker to access the device via FTP protocol.

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
How this class of weakness works · CWE-200

The application discloses data — error detail, internal paths, tokens, or other users' records — to someone who shouldn't see it. On its own it can look minor, but it hands attackers the map they need for a larger attack. Remediation is about minimising what's returned and enforcing authorization on every piece of data.

General guidance for the information exposure class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Accusine Pcsp Pfvp FirmwareOperating system
Affected:< 001.006.007
Accusine Pcsn Active Harmonic Filter FirmwareOperating system
Affected:< 002.002.004

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

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

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 001.006.007 / 002.002.004 or later
Fixed in 001.006.007002.002.004
Vendor patch download.schneider-electric.com →
Recommended fix High confidence

AccuSine PCS+/PFV+ firmware 001.006.007 or later; AccuSine PCSn firmware 002.002.004 or later

  1. 1. Identify the specific AccuSine model (PCS+ / PFV+ or PCSn) currently deployed
  2. 2. Determine the current firmware version by accessing the device interface or checking device documentation
  3. 3. Download the firmware update from the Schneider Electric support portal using the reference: https://download.schneider-electric.com/files?p_Doc_Ref=SEVD-2021-222-05
  4. 4. Review all upgrade prerequisites in the firmware release notes
  5. 5. Create a backup of the current device configuration
  6. 6. Schedule a maintenance window to minimize operational impact
  7. 7. Upload and install the new firmware following the manufacturer's documented upgrade procedure
  8. 8. After upgrade, verify the firmware version reflects the fixed release (V1.6.7 or later for PCS+/PFV+, V2.2.4 or later for PCSn)
Caveat Standard firmware upgrade risks apply - ensure configuration backup and planned maintenance window

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,250. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22793 — 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-2021-22793 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