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

CVE-2025-49280

HIGH · 8.1 CVSS v3.1 Published 2025-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in unfoldwp Magty magty allows PHP Local File Inclusion.This issue affects Magty: from n/a through <= 1.0.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 · high confidence

The Magty WordPress plugin up to version 1.0.6 contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in include/require statements. This allows remote attackers to include arbitrary files from the server filesystem, potentially leading to remote code execution if they can upload or control included files.

MitigationUpdate the Magty plugin to the latest patched version once available. Until then, disable the plugin or deploy a WAF rule to block path traversal patterns in request parameters. Apply principle of least privilege to file system permissions.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Verify Magty plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate the Magty plugin. Check the version number displayed. Alternatively, inspect the plugin main file header or read the version from the plugin's main PHP file.
    Affected if The installed version is 1.0.6 or lower, indicating the plugin contains the vulnerable code.
  2. Confirm Magty plugin is active
    Check if the Magty plugin is currently enabled in WordPress under Plugins > Installed Plugins. An active plugin processes requests and could be exploited.
    Affected if The plugin is active and running, enabling the LFI attack vector.
  3. Identify parameters accepting file paths
    Review the plugin's PHP source code, focusing on include, require, include_once, or require_once statements. Look for variables derived from $_GET, $_POST, or $_REQUEST that are used in these statements without proper sanitization.
    Affected if The plugin code accepts user input in include/require statements without validating for path traversal sequences like ../ or null bytes.
  4. Monitor HTTP requests for path traversal patterns
    Inspect incoming HTTP requests to the site, particularly to plugin endpoints. Search for patterns such as ../, ..\, or absolute paths in query parameters or POST data that could be used to include arbitrary files.
    Affected if Suspicious requests containing path traversal sequences targeting the plugin are observed in traffic or logs.
  5. Review web server access logs for LFI attempts
    Examine web server access logs (Apache, Nginx, or other) for entries containing the plugin's URL with file path arguments. Look for requests including /etc/passwd, ../../, or other sensitive filesystem paths.
    Affected if Logs show requests attempting to include files outside the web root, indicating active exploitation attempts.

You are affected if the Magty plugin version is 1.0.6 or lower and the plugin is currently active in your WordPress installation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Magty plugin to the latest patched version once available. Until then, disable the plugin or deploy a WAF rule to block path traversal patterns in request parameters. Apply principle of least privilege to file system permissions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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