CVE-2015-1613

NONECVSS 0.0

0.0

RhodeCode before 2.2.7 allows remote authenticated users to obtain API keys and other sensitive information via the (1) update_repo, (2) get_locks, or (3) get_user_groups API method.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 38.9%
KEV: Not listed

Published

February 16, 2015

Last Modified

May 6, 2026

References (2)

cve@mitrehttps://rhodecode.com/blog/rhodecode-enterprise-security-release/
af854a3a-2127-422b-91ae-364da2661108https://rhodecode.com/blog/rhodecode-enterprise-security-release/

Affected Packages

(1 across 1 ecosystem)

PyPI(1)

Package	Vulnerable range	Fixed in	Dependents
rhodecode	1.1.0 ... 2.2.6 (39 versions)	2.2.7	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 22:44 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-04 13:09 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:28 UTCEG score recompute
2026-05-28 13:28 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch

Frequently asked(4)

What is CVE-2015-1613?

CVE-2015-1613 is a none vulnerability published on February 16, 2015. RhodeCode before 2.2.7 allows remote authenticated users to obtain API keys and other sensitive information via the (1) updaterepo, (2) getlocks, or (3) getusergroups API method.

When was CVE-2015-1613 disclosed?

CVE-2015-1613 was first published in the National Vulnerability Database on February 16, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2015-1613 actively exploited?

CVE-2015-1613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2015-1613?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-1613, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-1613

Explore →

Is Your Infrastructure Affected by CVE-2015-1613?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2015-1613

📅 Published

🔄 Last Modified

🔗 References (2)

Affected Packages

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2015-1613?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(4)

Related CVEs(same CWE)