How severe is CVE-2021-3932?

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

Which packages are affected by CVE-2021-3932?

CVE-2021-3932 affects the following packages: area17/twill (Packagist), area17/twill (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-3932?

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

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

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

How do I mitigate CVE-2021-3932 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-3932 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2021-3932, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2021-3932 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th 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-3932?

CVE-2021-3932 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2021-3932?

A Metasploit module references CVE-2021-3932, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2021-3932 was published on November 13, 2021 and was last updated on July 8, 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-3932 — twill

MEDIUMFix: area17/twill@81d80d1

CVE-2021-3932 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in area17/twill. 1 public exploit reference exists, so weaponization risk is real. A fix is available for area17/twill — see the affected versions and patch details below.

twill is vulnerable to Cross-Site Request Forgery (CSRF)

Also known asGHSA-f99g-pg48-wrfc

Published

Nov 13, 2021

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

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

Real-World Exposure

2 pkgs affected

🐘area17/twill🐘area17/twill

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

twill is vulnerable to Cross-Site Request Forgery (CSRF)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`area17/twill`	all versions	1.2.5`composer require area17/twill:^1.2.5`
🐘Packagist	`area17/twill`	≥ 2.0.0&&< 2.5.3	2.5.3`composer require area17/twill:^2.5.3`

Affected Products

1 product · 1 configurations

Application

twillarea17

≤ 2.5.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

twill is vulnerable to Cross-Site Request Forgery (CSRF)

huntr.devNVDNov 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for area17/twill, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update area17/twill to 1.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-3932 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

twill is vulnerable to Cross-Site Request Forgery (CSRF)

O3 Security · Impact-Aware SCA

Is CVE-2021-3932 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

OpenSSF Scorecard

Package health score

twill

4.6/10

Code-Review2/10

Maintained4/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

Nov 13, 2021

First exploit

Nov 16, 2021

3 days after disclosure — rapid exploitation

Last updated

Jul 8, 2026

Identifiers

CVE-2021-3932

GHSA-f99g-pg48-wrfc

References

Advisorynvd.nist.gov Fixgithub.com Fixhuntr.dev Webgithub.com Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-352 are rated as high or higher (top: high).

CVE-2026-61593CVE-2026-59148CVE-2026-73222CVE-2026-73292CVE-2026-81890CVE-2026-19418CVE-2026-81888CVE-2026-55532Browse all CWE-352

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026

CVE-2021-3932 — twill

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-3932 in your dependencies?