Vulnerability · CVE-2012-2927
The TM Software Tempo plugin before 6.4.3.1, 6.5.x before 6.5.0.2, and 7.x before 7.0.3 for Atlassian JIRA does not properly restrict the capabilities of third-party X…
Published May 22, 2012 · catalog updated Jun 16, 2026 · tm software
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2012-2927. EPSS is 1.24%. Act only if a listed version of tm software is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-21728 · High
- CVE-2026-28377 · High
- Severity
- Medium4.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 1.24%
- Remediation
- Version ranges on file
- Affected products
- cpe tm software/tempo
The TM Software Tempo plugin before 6.4.3.1, 6.5.x before 6.5.0.2, and 7.x before 7.0.3 for Atlassian JIRA does not properly restrict the capabilities of third-party XML parsers, which allows remote authenticated users to cause a denial of service (resource consumption) via unspecified vectors.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe tm software/tempo2.2
- cpe tm software/tempo2.3
- cpe tm software/tempo2.3.1
- cpe tm software/tempo2.4.1
- cpe tm software/tempo2.5.1
- cpe tm software/tempo<= 6.4.3
How to fix CVE-2012-2927
Upgrade
CVE-2012-2927 lists a fix boundary at 6.4.3. Compare the installed build with that boundary before you change production.
Version check
Affected <= 6.4.3
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2012-2927. EPSS is 1.24%. Act only if a listed version of tm software is installed.
Which versions are affected?
Compare what you have installed with tm software/tempo 2.2; tm software/tempo 2.3; tm software/tempo 2.3.1; tm software/tempo 2.4.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-399. EPSS 1.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
May 22, 2012 · Monitored products — critical
Detected
The TM Software Tempo plugin before 6.4.3.1, 6.5.x before 6.5.0.2, and 7.x before 7.0.3 for Atlassian JIRA does not properly restrict the capabilities of third-party XML parsers, which allows remote authenticated users to cause a denial of service (resource consumption) via unspecified vectors.
Jun 16, 2026 · Monitored products — critical
Updated
The TM Software Tempo plugin before 6.4.3.1, 6.5.x before 6.5.0.2, and 7.x before 7.0.3 for Atlassian JIRA does not properly restrict the capabilities of third-party XML parsers, which allows remote authenticated users to cause a denial of service (resource consumption) via unspecified vectors.
Sources
- CVE.orgVulnerability recordCVE-2012-2927
Official CVE identifier
cve.org - Monitored products — criticalVendor advisoryCVE-2012-2927
The TM Software Tempo plugin before 6.4.3.1, 6.5.x before 6.5.0.2, and 7.x before 7.0.3 for Atlassian JIRA does not properly restrict the capabilities of third-party XML parsers, which allows remote authenticated users to cause a denial of service (resource consumption) via unspecified vectors.
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 4, 2026
- Monitored products — criticalNov 3, 2026