CVE-2022-30694
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 · uneditedThe login endpoint /FormLogin in affected web services does not apply proper origin checking. This could allow authenticated remote attackers to track the activities of other users via a login cross-site request forgery attack.
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 analysisThe application can't tell whether a state-changing request was genuinely intended by the user, so an attacker can trick a logged-in victim's browser into making it. That can transfer funds, change settings, or create accounts silently. Remediation is anti-CSRF tokens — or equivalent same-site protections — on every state-changing request.
General guidance for the cross-site request forgery (csrf) 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 dataall versionsall versionsall versions< 3.2.19< 3.2.19< 3.2.19< 3.2.19< 3.2.19CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 · scoped3.2.19
Firmware version 3.2.19 or later for affected PLC modules; contact Siemens for software controller and runtime patches
- Obtain the official vendor patch from https://cert-portal.siemens.com/productcert/pdf/ssa-478960.pdf for detailed instructions
- Identify the exact firmware version currently installed on each affected device (6es7154 8fb01 0ab0, 6es7154 8ab01 0ab0, 6es7154 8fx00 0ab0, 6es7151 8ab01 0ab0, 6es7151 8fb01 0ab0)
- Upgrade firmware on each affected device to version 3.2.19 or later
- For Simatic S7 1500 Software Controller, Simatic S7 Plcsim Advanced, and Simatic Wincc Runtime, contact Siemens directly for specific patch updates as these are software products rather than firmware-based devices
- After upgrading, verify that the /FormLogin endpoint now properly performs origin checking
- Test the login functionality to confirm the CSRF protection is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30694 — 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-30694 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