Templately Plugin up to 3.4.8 on WordPress JSON File save_template_to_file session_id/content_id/ai_page_ids improper authentication

Summaryinfo

A vulnerability was found in Templately Plugin up to 3.4.8 on WordPress and classified as critical. Affected is the function save_template_to_file of the component JSON File Handler. Executing a manipulation of the argument session_id/content_id/ai_page_ids can lead to improper authentication. This vulnerability is tracked as CVE-2026-0831. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical was found in Templately Plugin up to 3.4.8 on WordPress. This vulnerability affects the function save_template_to_file of the component JSON File Handler. The manipulation of the argument session_id/content_id/ai_page_ids with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at wordfence.com. This vulnerability was named CVE-2026-0831. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 01/10/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-1852). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• Templately Plugin

Version

• 3.4.0
• 3.4.1
• 3.4.2
• 3.4.3
• 3.4.4
• 3.4.5
• 3.4.6
• 3.4.7
• 3.4.8

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion