CVE-2013-2625 json
An Access Bypass issue exists in OTRS Help Desk before 3.2.4, 3.1.14, and 3.0.19, OTRS ITSM before 3.2.3, 3.1.8, and 3.0.7, and FAQ before…
published 6y ago modified 4mo ago also EUVD-2013-2564
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
An Access Bypass issue exists in OTRS Help Desk before 3.2.4, 3.1.14, and 3.0.19, OTRS ITSM before 3.2.3, 3.1.8, and 3.0.7, and FAQ before 2.2.3, 2.1.4, and 2.0.8. Access rights by the object linking mechanism is not verified
Patch / fix
- otrs faq 2.0.8, 2.1.4, 2.2.3
- otrs otrs_help_desk 3.0.19, 3.1.14, 3.2.4
- otrs otrs_itsm 3.0.7, 3.1.8, 3.2.3
- otrs2 Debian 11 3.1.7+dfsg1-8
debian advisories DEBIAN-CVE-2013-2625
- otrs openSUSE Tumbleweed 3.3.14-37.1
opensuse advisories openSUSE-SU-2024:10073-1
Is CVE-2013-2625 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.29% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
security-tracker.debian.org
/tracker/CVE-2013-2625
third-party-advisory
-
lists.opensuse.org
/opensuse-updates/2013-08/msg00027.html
release-notes, third-party-advisory
-
archives.neohapsis.com
/archives/bugtraq/2013-08/0009.html
broken-link, third-party-advisory
-
securityfocus.com
/bid/58936
third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/83287
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2013-2625
- NVD CVE-2013-2625
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.