CVE-2013-4869

UNRATEDCVSS · not yet scored

Also known asEUVD-2013-4714 (ENISA EUVD) · GHSA-563c-77qf-c6mg (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS v2: —Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2013 — use a compensating control (WAF / firewall / segmentation) and check the vendor's advisory.

The CVE record's description, written by its CNA (MITRE Corporation), states the affected versions: "Cisco Unified Communications Manager (CUCM) 7.1(x) through 9.1(2) and the IM & Presence Service in Cisco Unified Presence Server through 9.1(2) use the same CTI and database-encryption key across different customers' in…" No release containing a fix is confirmed on record.

Cisco Unified Communications Manager (CUCM) 7.1(x) through 9.1(2) and the IM & Presence Service in Cisco Unified Presence Server through 9.1(2) use the same CTI and database-encryption key across different customers' installations, which makes it easier for context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of this key, aka Bug IDs CSCsc69187 and CSCui01756. NOTE: the vendor has provided a statement that the "hard-coded static encryption key is considered a hardening issue rather than a vulnerability, and as such, has a CVSS score of 0/0."

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 18, 2013

Last Modified

April 29, 2026

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 169 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 74 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:27 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-10-31 16:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  3. 2026-10-30 16:27 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-29 16:27 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-28 16:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  6. 2026-10-27 16:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  7. 2026-10-26 16:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-25 16:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-25 13:50 UTCEG score recompute
  10. 2026-10-25 13:50 UTCGHSA enrichmentGHSA-563c-77qf-c6mg · GitHub severity LOW
  11. 2026-10-24 16:27 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  12. 2026-10-23 16:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-22 16:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-21 16:26 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  15. 2026-10-20 16:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-19 16:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-18 16:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-18 11:18 UTCEG score recompute
  19. 2026-10-17 16:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-16 16:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-10-15 16:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-10-14 16:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-10-13 16:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-10-12 21:22 UTCEG score recompute
  25. 2026-10-12 16:27 UTCEPSS rescoreEPSS 0.6% · 48th percentile
Show 70 more
  1. 2026-10-12 01:30 UTCEG score recompute
  2. 2026-10-11 13:39 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-10-09 20:01 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-08 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-07 23:39 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-06 15:11 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-05 17:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-04 23:16 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-09-30 14:58 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-09-30 00:14 UTCEG score recompute
  12. 2026-09-28 13:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-09-27 13:39 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-09-26 15:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-09-21 20:25 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-09-20 20:08 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-09-18 19:21 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-09-17 19:21 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-09-15 03:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-09-13 16:41 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-09-12 14:55 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-09-11 09:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-07 15:56 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-04 13:55 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-08-30 19:12 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  26. 2026-08-27 14:20 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  27. 2026-08-26 14:41 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  28. 2026-08-25 13:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  29. 2026-08-23 00:13 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  30. 2026-08-21 23:44 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-08-20 22:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  32. 2026-08-19 16:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  33. 2026-08-18 13:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  34. 2026-08-16 14:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  35. 2026-08-16 02:09 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-08-15 01:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  37. 2026-08-09 13:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  38. 2026-08-08 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  39. 2026-08-07 16:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  40. 2026-08-06 13:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  41. 2026-08-05 19:12 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  42. 2026-08-04 15:04 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  43. 2026-08-01 04:11 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  44. 2026-07-30 16:23 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-07-30 01:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-07-28 15:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  47. 2026-07-23 14:14 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  48. 2026-07-23 01:10 UTCEG score recompute
  49. 2026-07-23 00:14 UTCEG score recompute
  50. 2026-07-22 21:52 UTCEG score recompute
  51. 2026-07-22 14:04 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  52. 2026-07-21 15:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  53. 2026-07-20 17:03 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  54. 2026-07-19 14:27 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  55. 2026-07-19 02:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  56. 2026-07-18 10:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  57. 2026-07-16 16:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  58. 2026-07-15 16:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  59. 2026-07-15 01:56 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  60. 2026-07-13 22:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  61. 2026-07-13 06:08 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  62. 2026-07-12 05:42 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  63. 2026-07-09 19:05 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  64. 2026-07-08 15:10 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  65. 2026-07-07 13:41 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  66. 2026-07-06 02:19 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  67. 2026-07-05 02:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  68. 2026-07-04 06:27 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  69. 2026-07-02 15:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  70. 2026-07-01 15:02 UTCEPSS rescoreEPSS 0.6% · 45th percentile

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2013-4869?
CVE-2013-4869 is a vulnerability whose severity is not yet rated; its CVE record was published on July 18, 2013. Cisco Unified Communications Manager (CUCM) 7.1(x) through 9.1(2) and the IM & Presence Service in Cisco Unified Presence Server through 9.1(2) use the same CTI and database-encryption key across different customers' installations, which makes it easier for context-dependent attackers to defeat…
When was CVE-2013-4869 made public?
CVE-2013-4869 was made public on July 17, 2013: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 18, 2013. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2013-4869 actively exploited?
CVE-2013-4869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
How do I remediate CVE-2013-4869?
No fix for CVE-2013-4869 has been recorded since its CVE record was published in 2013. Restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and check the vendor's advisory for a fix. The CVE record's description, written by its CNA (MITRE Corporation), states the affected versions: "Cisco Unified Communications Manager (CUCM) 7.1(x) through 9.1(2) and the IM & Presence Service in Cisco Unified Presence Server through 9.1(2) use the same CTI and database-encryption key across different customers' in…" No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2013-4869

Explore →

Is Your Infrastructure Affected by CVE-2013-4869?

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

Book a Demo →Browse All CVEs