Security readout for executives and security teams
Plain-English summary
CVE-2026-0831 affects the Templately WordPress plugin through version 3.4.8. An unauthenticated attacker can cause the plugin to write limited JSON files inside the WordPress uploads directory. This is not described as remote code execution, but it can alter site content storage and create attacker-controlled files.
Executive priority
Treat this as a timely WordPress plugin maintenance issue, not a crisis. Prioritize internet-facing business sites using Templately, especially marketing or customer-facing sites. Remediate during the next security update window, sooner if suspicious files or logs are found.
Technical view
The issue is an unauthenticated arbitrary file write limited to .ai.json files under uploads. Sources attribute it to inadequate validation in save_template_to_file(), where session_id, content_id, and ai_page_ids influence file paths. CVSS is 5.3, network exploitable, low complexity, no privileges, no user interaction, integrity impact only.
Likely exposure
Public WordPress sites running Templately versions up to and including 3.4.8 are the relevant exposure. Risk is highest where the plugin is active and unauthenticated traffic can reach its AI content handling functionality.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is still practical to reach because it requires no authentication, no user interaction, and low attack complexity, but the file-write scope is described as limited.
Researcher notes
Public sources identify the vulnerable function and relevant code locations, plus a WordPress.org changeset. The provided affected metadata is incomplete, but the narrative states versions through 3.4.8 are affected. No source in the bundle proves active exploitation or names a specific fixed release.
Mitigation direction
- Identify all WordPress sites using the Templately plugin.
- Update Templately to a vendor-recommended version newer than 3.4.8, if available.
- If no fixed version is available, follow vendor guidance or temporarily disable the plugin.
- Restrict unnecessary public access to affected plugin functionality where operationally feasible.
- Back up the site before remediation and after confirming clean state.
Validation and detection
- Confirm installed Templately versions across production and staging sites.
- Check whether any installation is version 3.4.8 or earlier.
- Review uploads directories for unexpected .ai.json files.
- Review web logs for suspicious unauthenticated requests to Templately AI-related routes.
- Verify remediation by confirming the plugin version and vendor changelog or code changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0831 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/778242f4-5dfa-4d72-a032-8b5521c5b8ce?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/templately/tags/3.4.5/includes/Core/Importer/Utils/AIUtils.php#L414CVE reference
- https://plugins.trac.wordpress.org/browser/templately/tags/3.4.5/includes/API/AIContent.php#L38CVE reference
- https://plugins.trac.wordpress.org/changeset/3426051/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.