dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-0831

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Templately WordPress plugin contains an arbitrary file write vulnerability in the save_template_to_file() function. User-controlled parameters (session_id, content_id, ai_page_ids) are used to construct file paths without sanitization, allowing unauthenticated attackers to write arbitrary .ai.json files to locations within the uploads directory.

MitigationUpdate Templately plugin to version 3.4.9 or later. If an update is unavailable, consider disabling or removing the plugin until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Templately plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for the 'templately' folder, or query the wp_posts table for post_type = 'plugin' and post_name containing 'templately'
    Affected if The templately folder does not exist in wp-content/plugins/ and no plugin record exists in the database - the plugin is not installed and not vulnerable
  2. Identify installed Templately version
    Open the main plugin file (typically templately/includes/Plugin.php or templately/templately.php) and locate the 'Version:' header in the plugin comment block, or query the wp_options table for option_name = 'templately_version'
    Affected if The version number returned is lower than 3.4.9 (for example, 3.4.8, 3.4.7, 3.3.0, etc.) - the installed version is within the vulnerable range
  3. Confirm plugin is active
    Query the wp_options table for option_name = 'active_plugins' and check if the serialized array contains 'templately/templately.php', or check wp_options for option_name = 'templately_activation' with a non-empty value
    Affected if The plugin is active - the vulnerable save_template_to_file() function is accessible to unauthenticated requests
  4. Verify the vulnerable function exists
    Check if the file containing save_template_to_file() exists: look for templately/includes/Core/Export/Importer.php or similar paths that contain the function using grep or a file search, or attempt a safe test by examining plugin file integrity
    Affected if The save_template_to_file() function is present in the codebase - the arbitrary file write vulnerability exists in the code

A user is affected if the Templately plugin is installed, active, and the installed version is lower than 3.4.9, allowing unauthenticated arbitrary .ai.json file writes to the uploads directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Templately plugin to version 3.4.9 or later. If an update is unavailable, consider disabling or removing the plugin until a patch is released.

Recommended fix High confidence

Templately 3.4.9 or later (latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Templately plugin in the list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0831 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0831 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data