CVE-2017-15055

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 43% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

TeamPass before 2.1.27.9 does not properly enforce item access control when requesting items.queries.php. It is then possible to copy any arbitrary item into a directory controlled by the attacker, edit any item within a read-only directory, delete an arbitrary item, delete the file attachments of an arbitrary item, copy the password of an arbitrary item to the copy/paste buffer, access the history of an arbitrary item, and edit attributes of an arbitrary directory. To exploit the vulnerability, an authenticated attacker must tamper with the requests sent directly, for example by changing the "item_id" parameter when invoking "copy_item" on items.queries.php.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
60.6%
KEV
Not listed

Published

November 27, 2017

Last Modified

May 13, 2026

References (4)

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
nilsteampassnet/teampass2.1.21, 2.1.26, 2.1.272.1.27.9—

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-11 14:22 UTCOSV refresh
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-09 19:06 UTCEPSS rescore
  4. 2026-07-08 15:10 UTCEPSS rescore
  5. 2026-07-07 13:42 UTCEPSS rescore
  6. 2026-07-06 16:24 UTCEPSS rescore
  7. 2026-07-06 02:20 UTCEPSS rescore
  8. 2026-07-05 02:27 UTCEPSS rescore
  9. 2026-07-04 06:28 UTCEPSS rescore
  10. 2026-07-01 15:02 UTCEPSS rescore
  11. 2026-07-01 15:02 UTCEPSS rescore
  12. 2026-06-30 23:19 UTCEPSS rescore
  13. 2026-06-30 23:19 UTCEPSS rescore
  14. 2026-06-29 14:03 UTCEPSS rescore
  15. 2026-06-28 14:04 UTCEPSS rescore
  16. 2026-06-28 04:53 UTCEPSS rescore
  17. 2026-06-27 03:05 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-24 14:02 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 21:05 UTCOSV refresh
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-22 14:23 UTCEPSS rescore
  25. 2026-06-21 14:54 UTCEPSS rescore
Show 53 more
  1. 2026-06-21 14:54 UTCEPSS rescore
  2. 2026-06-21 01:57 UTCEPSS rescore
  3. 2026-06-21 01:57 UTCEPSS rescore
  4. 2026-06-19 19:23 UTCEPSS rescore
  5. 2026-06-19 19:23 UTCEPSS rescore
  6. 2026-06-18 17:50 UTCEPSS rescore
  7. 2026-06-17 17:50 UTCEPSS rescore
  8. 2026-06-16 17:50 UTCEPSS rescore
  9. 2026-06-15 17:45 UTCEPSS rescore
  10. 2026-06-14 23:14 UTCEPSS rescore
  11. 2026-06-14 23:14 UTCEPSS rescore
  12. 2026-06-13 22:57 UTCEPSS rescore
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-11 13:57 UTCEPSS rescore
  15. 2026-06-10 22:15 UTCEPSS rescore
  16. 2026-06-08 14:14 UTCEPSS rescore
  17. 2026-06-07 15:22 UTCEPSS rescore
  18. 2026-06-07 15:22 UTCEPSS rescore
  19. 2026-06-06 13:45 UTCEPSS rescore
  20. 2026-06-06 13:45 UTCEPSS rescore
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-06-05 11:57 UTCOSV refresh
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-05 06:08 UTCEPSS rescore
  25. 2026-06-04 13:10 UTCEPSS rescore
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-02 20:11 UTCEPSS rescore
  28. 2026-06-02 20:11 UTCEPSS rescore
  29. 2026-06-01 13:49 UTCEPSS rescore
  30. 2026-06-01 13:49 UTCEPSS rescore
  31. 2026-05-31 22:28 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-29 13:41 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-26 13:42 UTCEPSS rescore
  39. 2026-05-26 13:42 UTCEPSS rescore
  40. 2026-05-26 07:17 UTCEPSS rescore
  41. 2026-05-26 07:17 UTCEPSS rescore
  42. 2026-05-23 00:10 UTCEG score recompute
  43. 2026-05-22 21:15 UTCEPSS rescore
  44. 2026-05-22 21:15 UTCEPSS rescore
  45. 2026-05-22 21:15 UTCEPSS rescore
  46. 2026-05-22 07:41 UTCEG score recompute
  47. 2026-05-20 22:37 UTCEPSS rescore
  48. 2026-05-20 22:37 UTCEPSS rescore
  49. 2026-05-20 11:29 UTCOSV refresh
  50. 2026-05-20 11:21 UTCEPSS rescore
  51. 2026-05-20 11:21 UTCEPSS rescore
  52. 2026-05-18 21:30 UTCEPSS rescore
  53. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-15055?
CVE-2017-15055 is a high vulnerability published on November 27, 2017. TeamPass before 2.1.27.9 does not properly enforce item access control when requesting items.queries.php. It is then possible to copy any arbitrary item into a directory controlled by the attacker, edit any item within a read-only directory, delete an arbitrary item, delete the file attachments of…
When was CVE-2017-15055 disclosed?
CVE-2017-15055 was first published in the National Vulnerability Database on November 27, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-15055 actively exploited?
CVE-2017-15055 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-15055?
CVE-2017-15055 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2017-15055?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-15055, 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-2017-15055

Explore →

Is Your Infrastructure Affected by CVE-2017-15055?

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

Start Free Scan →Browse All CVEs