Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0831: CWE-863 Incorrect Authorization in wpdevteam Templately – Elementor & Gutenberg Template Library: 6500+ Free & Pro Ready Templates And Cloud!

0
Medium
VulnerabilityCVE-2026-0831cvecve-2026-0831cwe-863
Published: Sat Jan 10 2026 (01/10/2026, 09:22:18 UTC)
Source: CVE Database V5
Vendor/Project: wpdevteam
Product: Templately – Elementor & Gutenberg Template Library: 6500+ Free & Pro Ready Templates And Cloud!

Description

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.

AI-Powered Analysis

AILast updated: 01/18/2026, 07:45:50 UTC

Technical Analysis

CVE-2026-0831 is a vulnerability classified under CWE-863 (Incorrect Authorization) affecting the Templately plugin for WordPress, which provides a large library of Elementor and Gutenberg templates. The flaw exists in the save_template_to_file() function, where user-supplied parameters—session_id, content_id, and ai_page_ids—are used directly to construct file paths without proper sanitization or validation. This lack of input validation allows unauthenticated attackers to write arbitrary .ai.json files to arbitrary locations within the WordPress uploads directory. The uploads directory is typically writable by the web server, making it a prime target for such attacks. While the vulnerability does not directly compromise confidentiality or availability, it undermines integrity by enabling unauthorized file writes that could be used to inject malicious payloads, alter plugin behavior, or facilitate further exploitation such as code execution if combined with other vulnerabilities. The CVSS 3.1 base score is 5.3 (medium), reflecting network attack vector, no privileges required, no user interaction, and impact limited to integrity. No patches were linked at the time of reporting, and no known exploits in the wild have been documented. The vulnerability affects all versions up to and including 3.4.8 of the plugin, which is widely used in WordPress environments.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to the integrity of their WordPress-based websites. Attackers could leverage the arbitrary file write to insert malicious files that may alter website content, inject malicious scripts, or prepare the environment for further attacks such as privilege escalation or remote code execution. Public-facing websites using the Templately plugin are especially vulnerable, potentially leading to defacement, data manipulation, or reputational damage. While the vulnerability does not directly expose sensitive data, the integrity compromise could indirectly lead to confidentiality breaches if attackers use the foothold to escalate privileges. Organizations in sectors with high reliance on web presence—such as e-commerce, media, and government—may face operational disruptions or loss of customer trust. The absence of authentication requirements and ease of exploitation increase the likelihood of opportunistic attacks, particularly in environments where plugin updates are delayed or security monitoring is insufficient.

Mitigation Recommendations

1. Immediately update the Templately plugin to a patched version once released by the vendor. 2. Until a patch is available, restrict write permissions on the WordPress uploads directory to the minimum necessary, preventing unauthorized file creation. 3. Implement web application firewall (WAF) rules to detect and block suspicious requests attempting to exploit the vulnerable parameters (session_id, content_id, ai_page_ids). 4. Monitor the uploads directory for unexpected .ai.json files or other unusual file creations and investigate promptly. 5. Harden WordPress installations by disabling unnecessary plugins and enforcing least privilege principles for file system access. 6. Conduct regular security audits and vulnerability scans focusing on plugin vulnerabilities. 7. Educate site administrators on the importance of timely plugin updates and monitoring for security advisories. 8. Consider isolating critical WordPress instances or using containerization to limit the impact of potential compromises.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-09T20:31:20.483Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69621eda545d6fe96820a5a3

Added to database: 1/10/2026, 9:41:46 AM

Last enriched: 1/18/2026, 7:45:50 AM

Last updated: 2/7/2026, 4:16:57 AM

Views: 106

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats