How severe is CVE-2009-2737?

No CVSS score has been assigned to CVE-2009-2737 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2009-2737?

CVE-2009-2737 affects the following packages: roundup (PyPI), roundup (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2009-2737?

Update roundup to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-2737 is resolved across your whole dependency graph.

How do I detect CVE-2009-2737 in my PyPI dependencies?

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

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

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

CVE-2009-2737 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 84th 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-2009-2737?

CVE-2009-2737 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2009-2737 published, and has it been updated?

CVE-2009-2737 was published on May 2, 2022 and was last updated on July 6, 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

CVE-2009-2737 — roundup

CVE-2009-2737 is a CWE-264 vulnerability in roundup. A fix is available for roundup — see the affected versions and patch details below.

Roundup Improper Access Control

Also known asPYSEC-2026-744

Published

May 2, 2022

Updated

Jul 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐍roundup🐍roundup

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

The EditCSVAction function in cgi/actions.py in Roundup 1.2 before 1.2.1, 1.4 through 1.4.6, and possibly other versions does not properly check permissions, which allows remote authenticated users with edit or create privileges for a class to modify arbitrary items within that class, as demonstrated by editing all queries, modifying settings, and adding roles to users.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`roundup`	≥ 1.2&&< 1.2.1	1.2.1`pip install --upgrade 'roundup==1.2.1'`
🐍PyPI	`roundup`	≥ 1.4&&< 1.4.7	1.4.7`pip install --upgrade 'roundup==1.4.7'`

Affected Products

1 product · 8 configurations

Application

rounduptoni_mueller

8 versions

1.2.01.4.01.4.11.4.21.4.31.4.41.4.51.4.6

Detection & mitigation playbook

Open-source dependency

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

The EditCSVAction function in `cgi/actions.py` in Roundup 1.2 before 1.2.1, 1.4 through 1.4.6, and possibly other versions does not properly check permissions, which allows remote authenticated users with edit or create privileges for a class to modify arbitrary items within that class, as demonstrated by editing all queries, modifying settings, and adding roles to users.

O3 Security · Impact-Aware SCA

Is CVE-2009-2737 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works