How severe is CVE-2021-32697?

CVE-2021-32697 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-32697?

CVE-2021-32697 affects the following packages: neos/form (Packagist), neos/form (Packagist), neos/form (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-32697?

Update neos/form to 4.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32697 is resolved across your whole dependency graph.

How do I detect CVE-2021-32697 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/form, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-32697 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2021-32697 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-32697 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-32697?

CVE-2021-32697 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-32697?

CVE-2021-32697 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-32697 published, and has it been updated?

CVE-2021-32697 was published on June 21, 2021 and was last updated on July 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2021-32697 — form

MEDIUMFix: neos/form-ghsa-m5vx-8chx-qvmm#1

CVE-2021-32697 is a medium-severity (CVSS 5.3) Improper Input Validation vulnerability in neos/form. A fix is available for neos/form — see the affected versions and patch details below.

Form validation can be skipped

Also known asGHSA-m5vx-8chx-qvmm

Published

Jun 21, 2021

Updated

Jul 9, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-32697 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

🐘neos/form🐘neos/form🐘neos/form

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

By crafting a special GET request containing a valid form state, a form can be submitted without invoking any validators. We consider the severity low because it is not possible to change any form values since the form state is secured with an HMAC that is still verified. That means that this issue can only be exploited if Form Finishers cause side effects even if no form values have been sent.

Patches

https://github.com/neos/form/commit/69de4219b1f58157e2be6b05811463875d75c246

Workarounds

Form Finishers can be adjusted in a way that they only execute an action if the submitted form contains some expected data. Alternatively a custom Finisher can be added as first finisher.

References

This regression was introduced with https://github.com/neos/form/commit/049d415295be8d4a0478ccba97dba1bb81649567 Original report: https://tickets.neos.io/#ticket/zoom/411 (internal)

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`neos/form`	≥ 1.2.0&&< 4.3.3	4.3.3`composer require neos/form:^4.3.3`
🐘Packagist	`neos/form`	≥ 5.0.0&&< 5.0.9	5.0.9`composer require neos/form:^5.0.9`
🐘Packagist	`neos/form`	≥ 5.1.0&&< 5.1.3	5.1.3`composer require neos/form:^5.1.3`

Affected Products

1 product · 3 configurations

Application

formneos

≥ 5.1.0 && < 5.1.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/form, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update neos/form to 4.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32697 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact By crafting a special `GET` request containing a valid form state, a form can be submitted without invoking any validators. We consider the severity _low_ because it is not possible to _change_ any form values since the form state is secured with an HMAC that is still verified. That means that this issue can only be exploited if Form Finishers cause side effects even if no form values have been sent. ### Patches https://github.com/neos/form/commit/69de4219b1f58157e2be6b05811463875d75c246 ### Workarounds Form Finishers can be adjusted in a way that they only execute an action if th