How severe is CVE-2021-21360?

CVE-2021-21360 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-21360?

CVE-2021-21360 affects the following packages: products-genericsetup (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2021-21360?

Update products-genericsetup to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21360 is resolved across your whole dependency graph.

How do I detect CVE-2021-21360 in my PyPI dependencies?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

No public exploit code has been indexed for CVE-2021-21360 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-21360?

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

CVE-2021-21360 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2021-21360 was published on March 9, 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.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2021-21360 — products-genericsetup

MEDIUMFix: zopefoundation/Products.GenericSetup@7003195

CVE-2021-21360 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in products-genericsetup. A fix is available for products-genericsetup — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Products.GenericSetup

Also known asGHSA-jff3-mwp3-f8cwPYSEC-2021-43

Published

Mar 9, 2021

Updated

Jul 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk+0.04%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

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

Real-World Exposure

1 pkg affected

🐍products-genericsetup

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

Description

Impact

What kind of vulnerability is it? Who is impacted?

Information disclosure vulnerability - anonymous visitors may view log and snapshot files generated by the Generic Setup Tool.

Patches

Has the problem been patched? What versions should users upgrade to?

The problem has been fixed in version 2.1.1. Depending on how you have installed Products.GenericSetup, you should change the buildout version pin to 2.1.1 and re-run the buildout, or if you used pip simply do pip install "Products.GenericSetup>=2.1.1"

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Visit the ZMI Security tab at portal_setup/manage_access and click on the link Access contents information. On the next page, uncheck the box Also use roles acquired from folders containing this objects at the bottom and check the boxes for Manager and Owner. Then click on Save Changes. Return to the ZMI Security tab at portal_setup/manage_access and scroll down to the link View. Click on View, uncheck the box Also use roles acquired from folders containing this objects at the bottom and check the boxes for Manager and Owner. Then click on Save Changes.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Open an issue in the Products.GenericSetup issue tracker
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`products-genericsetup`	all versions	2.1.1`pip install --upgrade 'products-genericsetup==2.1.1'`

Affected Products

1 product · 1 configurations

Application

products.genericsetupzope

< 2.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for products-genericsetup, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update products-genericsetup to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21360 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ Information disclosure vulnerability - anonymous visitors may view log and snapshot files generated by the Generic Setup Tool. ### Patches _Has the problem been patched? What versions should users upgrade to?_ The problem has been fixed in version 2.1.1. Depending on how you have installed Products.GenericSetup, you should change the buildout version pin to 2.1.1 and re-run the buildout, or if you used pip simply do pip install `"Products.GenericSetup>=2.1.1"` ### Workarounds _Is there a way for users to fix or remediate the v