dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-13790

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 MinimogWP – The High Converting eCommerce WordPress Theme theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.7.0 via the 'template' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 MinimogWP WordPress theme versions up to 3.7.0 contains a Local File Inclusion (LFI) vulnerability in the 'template' parameter that allows unauthenticated attackers to include arbitrary server files. This can be chained to achieve remote code execution by including maliciously crafted files, enabling complete server compromise.

MitigationUpdate the MinimogWP theme to version 3.7.1 or later. If immediate patching is not possible, disable the theme or implement web application firewall rules to block requests with the 'template' parameter.

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
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 installed MinimogWP theme version
    Check the theme version in WordPress admin under Appearance > Themes, or inspect the style.css file in wp-content/themes/minimogwp/ and look for the 'Version:' declaration
    Affected if The version number is 3.7.0 or lower
  2. Locate vulnerable template parameter handling
    Search theme PHP files for code that processes a 'template' parameter, typically using include(), require(), or similar functions. Look in core theme files for $_GET['template'] or $_REQUEST['template'] usage
    Affected if The theme contains code that directly uses the 'template' parameter from user input in include/require statements without validation
  3. Verify the LFI vulnerability is exploitable
    Send a crafted HTTP request to any page using the theme with a parameter such as ?template=../../../../wp-config.php (or similar path traversal) to test if arbitrary files can be included
    Affected if The server returns content from the targeted file, confirming unauthenticated file inclusion is possible
  4. Check if the vulnerability is exposed to the internet
    Review web server logs and firewall records for requests containing 'template=' parameter patterns, especially from external IP addresses
    Affected if Unauthenticated external requests with the template parameter are being logged or reaching the application

A user is affected if the MinimogWP theme version is 3.7.0 or lower AND the theme processes the 'template' parameter without proper sanitization, allowing unauthenticated file inclusion.

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 MinimogWP theme to version 3.7.1 or later. If immediate patching is not possible, disable the theme or implement web application firewall rules to block requests with the 'template' parameter.

Recommended fix High confidence

MinimagWP theme version 3.7.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Locate the MinimogWP theme
  4. If a newer version is available, click on the theme and select Update Now, or download version 3.7.1+ from the theme vendor
  5. Alternatively, upload the fixed theme version via Appearance > Themes > Add New > Upload Theme
  6. After updating, verify the theme version shows 3.7.1 or higher in Themes section
  7. Check that the site frontend and admin still function correctly
Caveat Standard theme update - review custom child theme or template overrides after upgrade

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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