Skip to content
Emerging threatsMedium

CVE-2014-2314Jira Path Traversal

Directory traversal vulnerability in the Issue Collector plugin in Atlassian JIRA before 6.0.4 allows remote attackers to create arbitrary files via unspecified vectors.

Published Mar 9, 2014 · Updated May 6, 2026

Key Facts

Routine patching
  • CVE-2014-2314 is a medium-severity vulnerability (CVSS 4.3 v2) affecting Jira (Atlassian).
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 26% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Jira 6.0.3.
  • Brandefense priority: routine patching, as no exploitation is known and its severity is moderate or low.

Scores

CVSS v2

4.3

AV:N/AC:M/Au:N/C:N/I:P/A:N

EPSS (30-day exploit likelihood)

26%

Higher than 97.9% of all scored CVEs

Exploit maturity

Weaponized

ATLAS score

47/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Weaponized

Public exploit code

3

Proof-of-concept links

In-the-wild evidence

1

Reports of active use

Description

Directory traversal vulnerability in the Issue Collector plugin in Atlassian JIRA before 6.0.4 allows remote attackers to create arbitrary files via unspecified vectors.

Affected Products

4 affected entries in total
ProductAffected versionsFixed in
JiraAtlassian6.0, 6.0.1, 6.0.26.0.3

Patched Releases

Jira

6.0.3

Timeline

  1. Publicly disclosed

    Mar 9, 2014

  2. Last updated

    May 6, 2026

Weakness Type

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

FAQ

Common Questions.

Is CVE-2014-2314 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.