NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2016-3953 — web2py

CRITICALFix: web2py/web2py@9706d12

CVE-2016-3953 is a critical-severity (CVSS 9.8) Hard-coded Credentials vulnerability in web2py. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for web2py — see the affected versions and patch details below.

web2py remote code execution via hardcoded encryption key in session.connect function

Also known asGHSA-q2rq-qgcf-m22wPYSEC-2026-570
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk
0.95%1.94%2.94%3.94%1.5%3.3%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍web2py

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 sample web application in web2py before 2.14.2 might allow remote attackers to execute arbitrary code via vectors involving use of a hardcoded encryption key when calling the session.connect function.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIweb2pyall versions2.14.2pip install --upgrade 'web2py==2.14.2'

Affected Products

1 product · 1 configurations
Application
web2pyweb2py
< 2.14.2
range
Exploits & PoCs
1

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

The sample web application in web2py before 2.14.2 might allow remote at…

devco.reNVDJun 2019

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update web2py to 2.14.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-3953 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

The sample web application in web2py before 2.14.2 might allow remote attackers to execute arbitrary code via vectors involving use of a hardcoded encryption key when calling the session.connect function.
O3 Security · Impact-Aware SCA

Is CVE-2016-3953 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2016-3953: web2py RCE — Fixed in 2.14.2