HomeWordPress vulnerabilitiesTemplately
Templately vulnerabilities
Templately has 4 known vulnerabilities in this database. The most recent published record is dated 15 Aug 2026.
- Known vulnerabilities
- 4
- Active installs
- 300,000+
- Latest version
- 3.8.0
- Last updated
- 24 Sep 2026
- Most recent
- 15 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-18438 | High 8.8 | Up to 3.7.1 | Fixed in a later version (latest 3.8.0) | 15 Aug 2026 |
| Broken access control CVE-2026-15359 | Medium 6.5 | Before 3.7.1 | Fixed in 3.7.1 | 7 Aug 2026 |
| Broken access control CVE-2026-0831 | Medium 5.3 | Up to 3.4.8 | Fixed in a later version (latest 3.8.0) | 10 Jan 2026 |
| Broken access control CVE-2023-5454 | High 7.5 | Before 2.2.6 | Fixed in 2.2.6 | 6 Nov 2023 |
Read the published descriptions
- CVE-2026-18438, 15 Aug 2026
- 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. CVE record
- CVE-2026-15359, 7 Aug 2026
- The Templately WordPress plugin before 3.7.1 does not have an authorisation check on one of its request handlers, allowing unauthenticated attackers to overwrite the administrator's stored cloud service connection with an account under their control, disconnecting the legitimate administrator and redirecting the site's cloud template library to attacker-controlled content. CVE record
- CVE-2026-0831, 10 Jan 2026
- The Templately plugin for WordPress is vulnerable to Arbitrary File Write in all versions up to, and including, 3.4.8. This is due to inadequate input validation in the `save_template_to_file()` function where user-controlled parameters like `session_id`, `content_id`, and `ai_page_ids` are used to construct file paths without proper sanitization. This makes it possible for unauthenticated attackers to write arbitrary `.ai.json` files to locations within the uploads directory. CVE record
- CVE-2023-5454, 6 Nov 2023
- The Templately WordPress plugin before 2.2.6 does not properly authorize the `saved-templates/delete` REST API call, allowing unauthenticated users to delete arbitrary posts. CVE record
What to do if you run Templately
If you run Templately, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Templately vulnerabilities
Free. We email you when a new vulnerability is published for Templately, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.