CVE-2026-0831

Templately <= 3.4.8 - Unauthenticated Limited Arbitrary JSON File Write

2026-01-09 20:32
type5afe

Strategic Overview

Status
Patched in 3.4.9
Affected Plugin
Templately – Elementor & Gutenberg Template Library: 6500+ Free & Pro Ready Templates And Cloud!
Affected Version
<= 3.4.8
CVSS
5.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2026-0831
View all Templately – Elementor & Gutenberg Template Library: 6500+ Free & Pro Ready Templates And Cloud! vulnerabilities

At a glance

CVE-2026-0831 is a medium-severity Incorrect Authorization vulnerability in the Templately WordPress plugin, affecting versions <= 3.4.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.4.9; sites on affected versions should update now. Disclosed January 2026, reported by type5afe.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-863: Incorrect Authorization

Templately <= 3.4.8 carries this weakness at save_template_to_file(), and reaching it takes no account at all. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For Templately the fix is 3.4.9: builds <= 3.4.8 are affected, anything from 3.4.9 onward is not.

Remediation

Update to version 3.4.9, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Templately 3.4.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-0831https://www.wordfence.com/threat-intel/vulnerabilities/id/778242f4-5dfa-4d72-a032-8b5521c5b8cehttps://nvd.nist.gov/vuln/detail/CVE-2026-0831

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C