CVE-2022-39051 | Perl Code execution in Template Toolkit

Attacker might be able to execute malicious Perl code in the Template toolkit, by having the admin installing an unverified 3th party package

Published: 2022-09-05 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-39051 is rated Moderate Risk (43.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.66%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-39051

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.46% 0.66% +0.21%
2 2025-12-28 0.39% 0.46% +0.07%
3 2025-12-27 — 0.39% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-39051

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.9 5.9 [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2022-39051

OS Trackers for CVE-2022-39051

vendor priority summary link
ubuntu medium CVE-2022-39051 medium priority: Ubuntu including 1 source packages (znuny), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, DNE 3, needs-triage 3. https://ubuntu.com/security/CVE-2022-39051

Affected software / configurations for CVE-2022-39051

Vendor Product Version Raw CPE
otrs otrs >= 6.0.0, <= 6.0.32 cpe:2.3:a:otrs:otrs:*:*:*:*:community:*:*:*
otrs otrs >= 7.0.0, < 7.0.37 cpe:2.3:a:otrs:otrs:*:*:*:*:*:*:*:*
otrs otrs >= 8.0.0, < 8.0.25 cpe:2.3:a:otrs:otrs:*:*:*:*:*:*:*:*

References for CVE-2022-39051

cvelogic Threat Intelligence