dbcve.org
Starter TemplatesWordPress extension · Fancywp

CVE-2024-13924

CRITICAL · 9.1 CVSS v3.1 Published 2025-03-08
Fix available
A fix is available. Upgrade to after 2.0.0 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
The Starter Templates by FancyWP plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 2.0.0 via the 'http_request_host_is_external' filter. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 by FancyWP WordPress plugin (versions up to 2.0.0) contains a Blind SSRF vulnerability via the 'http_request_host_is_external' filter, allowing unauthenticated attackers to make the server perform arbitrary HTTP requests to internal or external services and potentially exfiltrate data.

MitigationUpdate the plugin to version 2.0.1 or later. If immediate patching is not possible, consider disabling the plugin or deploying WAF rules to filter outbound requests to internal network ranges.

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
Starter TemplatesWordPress extension
Affected:<= 2.0.0

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 plugin installation
    Navigate to WordPress admin > Plugins and look for 'Starter Templates by FancyWP' or check the wp-content/plugins/ directory for a folder containing 'fancywp' or 'starter-templates'
    Affected if The plugin is installed on the WordPress site
  2. Identify installed version
    Open the main plugin file (usually in wp-content/plugins/fancywp-starter-templates/ or similar) and check the 'Version' header in the plugin comment block, or check the readme.txt file for the version number
    Affected if The version is 2.0.0 or lower
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the plugin status shows as 'Active'
    Affected if The plugin is currently active and processing requests
  4. Check for suspicious outbound requests
    Review server access logs and web application firewall logs for unusual outbound HTTP requests originating from the server, particularly to internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x) or metadata endpoints
    Affected if There are outbound requests from the server to internal resources that were not initiated by legitimate admin actions

A site is affected if the FancyWP Starter Templates plugin version 2.0.0 or lower is installed and active on the WordPress site, allowing potential unauthenticated SSRF attacks via the http_request_host_is_external filter.

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 a release after 2.0.0
Interim mitigation

Update the plugin to version 2.0.1 or later. If immediate patching is not possible, consider disabling the plugin or deploying WAF rules to filter outbound requests to internal network ranges.

Recommended fix Moderate confidence

Version higher than 2.0.0

  1. Log in to the WordPress admin dashboard.
  2. Navigate to the 'Plugins' menu.
  3. Locate 'Starter Templates by FancyWP' in the list of installed plugins.
  4. Click 'Update Now' to install the latest available version.
  5. Alternatively, download the latest plugin version from the WordPress Plugin Repository and upload it to replace the current installation.

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

Fix this in Starter Templates Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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