dbcve.org
TemplatelyWordPress extension

CVE-2024-47308

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 3.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in WPDeveloper Templately templately.This issue affects Templately: from n/a through <= 3.1.2.

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 · moderate confidence

Missing Authorization vulnerability in WPDeveloper Templately plugin version 3.1.2 and below. The plugin fails to properly enforce authorization checks, allowing attackers to potentially access or modify data or functionality they should not have permission to access. The critical CVSS score of 9.8 suggests unauthenticated attackers can exploit this to perform privileged actions.

MitigationUpdate Templately to the latest version when available. As an immediate workaround, restrict access to the plugin through server-level access controls or disable the plugin if not essential. Review user roles and capabilities for any WordPress site using this plugin.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TemplatelyWordPress extension
Affected:< 3.1.3

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Templately plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'templately' or search for 'Templately' in the WordPress admin under Plugins > Installed Plugins
    Affected if The Templately plugin folder exists in the WordPress plugins directory or appears in the plugins list
  2. Determine the installed version
    Open the main plugin file (typically templately.php) and locate the 'Version' header in the plugin comment block, or view the version displayed in the WordPress admin plugins list
    Affected if The version number is lower than 3.1.3 (e.g., 3.1.2, 3.1.1, 3.0.x, etc.)
  3. Verify if the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to see if Templately shows as 'Active', or query the wp_options table for option_name='active_plugins' and check if templately is included
    Affected if The plugin is currently activated on the WordPress site
  4. Review WordPress user accounts for unauthorized admin creation
    Navigate to Users > All Users in the WordPress admin and examine the list of administrators, or query the wp_users and wp_usermeta tables to list all users with wp_capabilities containing 'administrator'
    Affected if Unexpected or unknown administrator accounts exist that were not created by legitimate site administrators

A site is affected if Templately plugin version 3.1.2 or lower is installed and active, since the missing authorization flaw allows unauthenticated attackers to perform privileged actions.

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
Upgrade available Upgrade to 3.1.3 or later
Fixed in 3.1.3
Interim mitigation

Update Templately to the latest version when available. As an immediate workaround, restrict access to the plugin through server-level access controls or disable the plugin if not essential. Review user roles and capabilities for any WordPress site using this plugin.

Recommended fix High confidence

Templately 3.1.3

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress Admin Dashboard > Plugins section
  3. Locate the Templately plugin in your installed plugins list
  4. Click 'Update now' on the Templately plugin if an update is available, or manually upload version 3.1.3 or higher
  5. Verify the plugin updated successfully by checking the version number in the Plugins list
  6. Test that the Templately functionality works as expected on your site

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

Fix this in Templately Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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