VDB

CVE-2016-3954

CVE-2016-3954 PUBLISHED CVSS 5.5 MEDIUM

web2py exposure of sensitive information

Reported by mitre · Published February 6, 2018

web2py is fixed in 2.14.2 (PyPI)

web2py before 2.14.2 allows remote attackers to obtain the session_cookie_key value via a direct request to examples/simple_examples/status. NOTE: this issue can be leveraged by remote attackers to execute arbitrary code using CVE-2016-3957.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
web2pyPyPI2.14.2
web2pyweb2py2.14.2
web2pyUbuntu:16.04:LTS2.12.3-1ubuntu0.1

Risk scores

CVSS 3.0
5.5
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

VendorProductVersions
n/an/an/a
PyPIweb2py0
n/an/a*

Timeline

  • Feb 6, 2018 CVE Published
  • Feb 4, 2022 EPSS Score (30 in total, the first dated here)
  • Jul 16, 2025 CVE Updated
  • Mar 5, 2026 Distribution Patch
  • Mar 5, 2026 Security Advisory (2 in total, the first dated here)
  • Oct 8, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2016-3954
vulnetix vdb fixes CVE-2016-3954

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2016-3954/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›