dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-2334

MEDIUM · 6.4 CVSS v3.1 Published 2024-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 Template Kit – Import plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the template upload functionality in all versions up to, and including, 1.0.14 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Template Kit – Import WordPress plugin suffers from a stored XSS vulnerability in its template upload functionality. Attackers with author-level WordPress permissions can inject malicious JavaScript via insufficiently sanitized template inputs, which then executes when other users access affected pages.

MitigationUpdate to version 1.0.15 or later which patches the input sanitization and output escaping gaps. Until patched, restrict template upload permissions to administrator-level accounts only.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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. Confirm the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Template Kit - Import' or check the plugins directory via file system for the template-kit-import folder
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    In WordPress admin, click on the plugin name/link in the Plugins list to view version details, or read the main plugin PHP file header for the Version field
    Affected if Version is lower than 1.0.15 (vulnerable versions) or version cannot be determined (assume vulnerable)
  3. Review user roles with template upload capability
    Navigate to WordPress Users > Roles or check role capabilities. Look for users with 'upload_files' capability at Author level or higher who have access to the Template Kit Import functionality
    Affected if Any user role below Administrator (such as Author, Editor, Contributor) has permissions to upload templates via this plugin
  4. Inspect uploaded template files for suspicious content
    Access the Template Kit library or uploaded templates area. Manually review template files (JSON/XML) for unexpected script tags, event handlers, or encoded JavaScript payloads
    Affected if Templates contain unsanitized script tags, javascript: URLs, or event handler attributes like onload/onerror
  5. Check for unexpected template imports in the library
    Review the Template Kit Import library for templates you do not recognize or that were imported by unknown authors
    Affected if Unknown templates exist in the library from untrusted users or from timeframes you do not recognize

You are affected if the plugin version is below 1.0.15 AND any non-Administrator user role has template upload permissions, or if malicious scripts are found in imported templates.

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 to version 1.0.15 or later which patches the input sanitization and output escaping gaps. Until patched, restrict template upload permissions to administrator-level accounts only.

Recommended fix High confidence

1.0.15

  1. Log in to the WordPress admin dashboard with an account that has administrator privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Template Kit – Import' plugin in the list
  4. Check the current version number displayed under the plugin name
  5. If the installed version is 1.0.14 or earlier, click 'Update now' if an update is available, or manually download version 1.0.15 or later from the WordPress plugin repository
  6. After updating, verify the new version number reflects the update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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