How severe is CVE-2018-20613?

CVE-2018-20613 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2018-20613 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-20613?

CVE-2018-20613 affects Temmoku Project Temmoku. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2018-20613?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2018-20613 published?

CVE-2018-20613 was published on 2018-12-30 and last updated on 2026-06-17.

CVE-2018-20613

CVE-2018-20613 is a high-severity vulnerability in Temmoku Project Temmoku with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.8
EPSS exploit prediction: 0% (39th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-352
Affected product: Temmoku Project Temmoku
Published: 2018-12-30
Last modified: 2026-06-17

Description

TEMMOKU T1.09 Beta allows admin/user/add CSRF.

Frequently asked questions

What is CVE-2018-20613?: TEMMOKU T1.09 Beta allows admin/user/add CSRF.
How severe is CVE-2018-20613?: CVE-2018-20613 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-20613 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-20613?: CVE-2018-20613 affects Temmoku Project Temmoku. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-20613?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-20613 published?: CVE-2018-20613 was published on 2018-12-30 and last updated on 2026-06-17.

References

https://github.com/AvaterXXX/CVEs/blob/master/temmoku.md

Affected products (1)

cpe:2.3:a:temmoku_project:temmoku:t1.09:beta:*:*:*:*:*:*

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

CVE-2025-32642 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This…
CVE-2025-23922 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a…
CVE-2017-5145 — Critical (CVSS 10.0): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware…
CVE-2019-25729 — Critical (CVSS 9.8): PDF Signer 3.0 contains a server-side template injection vulnerability that allows unauthenticated attackers to execute…
CVE-2025-48340 — Critical (CVSS 9.8): Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager user-profile-meta allows…
CVE-2025-2907 — Critical (CVSS 9.8): The Order Delivery Date WordPress plugin before 12.3.1 does not have authorization and CSRF checks when importing…

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →