8.8

CVE-2026-18438: wordpress templately

CVSS: 8.8v3.1HighDeferred
Published 15-08-2026Last modified 17-08-2026

Vulnerability summary

CVE-2026-18438 is a high (CVSS 8.8) vulnerability in wordpress templately. EPSS estimates a 1.31% chance of exploitation in the next 30 days, higher than 70.2% of scored vulnerabilities. Fixed in 3.7.2.

Overall risk
35/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.8/10
010
High · v3.1 (CVE.org)
EPSS score
1.31%
0%100%
Low · +0.41 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Timeline

  1. 15-08-2026
    PublishedVulnerability first disclosed.
  2. 17-08-2026
    Last modifiedVulnerability information updated.

Description

The Templately – Elementor & Gutenberg Template Library: 6500+ Free & Pro Ready Templates And Cloud! plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 3.7.1 via the fetch_remote_file function. This is due to a filename validation/destination mismatch in fetch_remote_file, where file type validation is performed against the attacker-controlled Content-Disposition filename rather than the URL-path-derived destination filename. This makes it possible for authenticated attackers, with contributor-level access and above, to execute code on the server. A GIF+PHP polyglot file passes wp_check_filetype_and_ext validation as image/gif via the Content-Disposition filename, while the actual destination path is written with a .php extension derived from the URL path, bypassing the unfiltered_upload capability gate entirely. The affected endpoints are reachable at this privilege level because Templately's entire REST API — including the cloud import endpoints used in this attack (/templately/v1/clouds/upload and /templately/v1/insert) — is authorized only by a current_user_can('delete_posts') check, with no administrator or manage_options capability requirement. The same permission gate also allows a contributor to overwrite the site's global Templately cloud connection via the /templately/v1/login endpoint with global_signin set to true. A complete remediation should both correct fetch_remote_file to validate the file type against the actual destination filename rather than the Content-Disposition header (and avoid deriving the write path from the request URL), and restrict state-changing Templately REST routes to an appropriate administrator-level capability.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

1.31%

Chance of exploitation in the next 30 days

Percentile

70%

Versus all other CVEs

30-day change

+0.41 pp

From 0.90% on 20-09-2026

20-09-202620-10-2026
EPSS score
1.31%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Wordpress1 product
  • templately≤ 3.7.1 (fixed in 3.7.2)
Wpdevteam1 product
  • templately – elementor & gutenberg template library: 6500+ free & pro ready templates and cloud!≤ 3.7.1

2 vendors · 2 products

References

19 links
Show all 19 references