dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-13065

HIGH · 8.8 CVSS v3.1 Published 2025-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Starter Templates plugin for WordPress is vulnerable to arbitrary file upload in all versions up to, and including, 4.4.41. This is due to insufficient file type validation detecting WXR files, allowing double extension files to bypass sanitization while being accepted as a valid WXR file. This makes it possible for authenticated attackers, with author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Starter Templates WordPress plugin (versions up to 4.4.41) has an arbitrary file upload vulnerability allowing authenticated users with author-level access to upload malicious files. The flaw stems from insufficient file type validation for WXR (WordPress eXtended RSS) import files, where double extension files (e.g., shell.php.jpg) can bypass sanitization checks while being accepted as valid WXR files, enabling remote code execution.

MitigationUpdate the Starter Templates plugin to version 4.4.42 or later. Until updated, limit upload capabilities to administrator-level users only and monitor for suspicious file uploads.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Starter Templates plugin is installed
    Navigate to WordPress admin > Plugins and locate Starter Templates in the list of installed plugins
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In the Plugins page, view the Starter Templates plugin details to read the Version number, or inspect the plugin main file for the Version header
    Affected if Version is 4.4.41 or lower (any version up to and including 4.4.41)
  3. Confirm WXR import feature is accessible
    Locate the import functionality within Starter Templates plugin (typically under Starter Templates menu in admin), typically labeled as Import Site Templates or similar WXR import option
    Affected if The WXR import feature exists and is accessible in the plugin
  4. Identify user roles with import access
    Check WordPress user roles and their capabilities. Navigate to Users > All Users and verify which roles (Author, Editor, Contributor) can access the Starter Templates import functionality
    Affected if Users with Author-level access or higher can use the WXR import feature

Your environment is affected if Starter Templates plugin version 4.4.41 or lower is installed AND the WXR import feature is accessible to users with Author-level permissions or above.

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 the Starter Templates plugin to version 4.4.42 or later. Until updated, limit upload capabilities to administrator-level users only and monitor for suspicious file uploads.

Recommended fix Moderate confidence

Starter Templates version 4.4.42 or later

  1. 1. Log in to the WordPress admin dashboard with an account that has administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Starter Templates' plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/starter-templates/ and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the new version number is displayed in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13065 — 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-2025-13065 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