CVE-2026-0831: 
WordPress vulnerability analysis and mitigation

CVE-2026-0831 is an Arbitrary File Write vulnerability in the Templately plugin for WordPress, affecting all versions up to and including 3.4.8. The flaw resides in the save_template_to_file() function, where user-controlled parameters (session_id, content_id, ai_page_ids) are used to construct file paths without proper sanitization, enabling unauthenticated attackers to write arbitrary .ai.json files to the uploads directory. It was published on January 10, 2026, and assigned by Wordfence. The CVSS v3.1 base score is 5.3 (Medium), assigned by Wordfence (Wordfence).

The root cause is classified as CWE-863 (Incorrect Authorization), stemming from inadequate input validation in the save_template_to_file() function within includes/Core/Importer/Utils/AIUtils.php (line 414) and the API handler in includes/API/AIContent.php (line 38). User-supplied parameters — session_id, content_id, and ai_page_ids — are incorporated directly into file path construction without sanitization, allowing path traversal-style manipulation to place .ai.json files in arbitrary locations within the uploads directory. No authentication is required to trigger this endpoint, making the attack vector fully unauthenticated over the network with low complexity (Wordfence, WordPress Trac).

Successful exploitation allows unauthenticated attackers to write arbitrary .ai.json files to locations within the WordPress uploads directory, resulting in a low integrity impact with no direct confidentiality or availability impact per the CVSS scoring. While the file type is restricted to .ai.json, malicious content written to the uploads directory could be leveraged for stored payload delivery, template injection, or as a stepping stone for further attacks if the JSON content is later processed by the application. The scope is limited to the affected WordPress installation's uploads directory (Wordfence).

No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been reported as of the available data. The EPSS score is approximately 0.026% (0.000260), indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been identified (Wordfence).

1. Reconnaissance: Identify WordPress sites running the Templately plugin (versions ≤ 3.4.8) using tools like WPScan, Shodan, or by checking /wp-content/plugins/templately/ for version indicators.
2. Identify the vulnerable endpoint: Locate the API endpoint that invokes save_template_to_file() in includes/API/AIContent.php — this endpoint accepts unauthenticated requests.
3. Craft malicious request: Send an HTTP POST request to the vulnerable API endpoint with manipulated parameters (session_id, content_id, ai_page_ids) crafted to control the resulting file path within the uploads directory.
4. Write malicious file: The unsanitized parameters cause the server to write an attacker-controlled .ai.json file to a chosen location within the WordPress uploads directory.
5. Leverage written file: Depending on application behavior, the written JSON file may be processed by the plugin or served to other users, potentially enabling stored payload delivery or further exploitation (Wordfence, Infinit Security).

• Network: Unexpected or anomalous POST requests to the Templately AI content API endpoint from unauthenticated sources; repeated requests with varying session_id, content_id, or ai_page_ids parameter values.
• File System: Unexpected .ai.json files appearing in the WordPress uploads directory (/wp-content/uploads/) with unusual names or in unexpected subdirectories; file creation timestamps inconsistent with normal plugin activity.
• Logs: WordPress or web server access logs showing POST requests to the Templately API endpoint from unknown or suspicious IP addresses, particularly with unusual parameter values in the request body.

Users should update the Templately plugin to version 3.4.9 or later, which addresses the insufficient input validation in the save_template_to_file() function. The fix is available via the WordPress plugin repository changeset 3426051. As an interim measure, site administrators can disable the Templately plugin until the update is applied, or restrict access to the WordPress uploads directory to prevent serving of unexpected .ai.json files (WordPress Trac, Wordfence).

Sucuri included CVE-2026-0831 in their January 2026 vulnerability patch roundup, highlighting it as a notable WordPress plugin issue requiring prompt patching (Sucuri Blog). Infinit Security published a dedicated technical post detailing the vulnerability mechanics (Infinit Security). Community discussion was limited, with the vulnerability receiving standard aggregation coverage across CVE tracking platforms.