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

CVE-2025-49036

HIGH · 8.1 CVSS v3.1 Published 2025-08-14
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 octagonwebstudio Premium Addons for KingComposer premium-addons-for-kingcomposer allows PHP Local File Inclusion.This issue affects Premium Addons for KingComposer: from n/a through <= 1.1.1.

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

This is a Local File Inclusion (LFI) vulnerability in the Premium Addons for KingComposer WordPress plugin. The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file path parameters to include arbitrary local PHP files. This can lead to code execution if an attacker can upload or control included files.

MitigationUpgrade to a patched version of Premium Addons for KingComposer. If no patch is available, implement input validation using allowlists for file paths and disable PHP execution in upload directories to limit exploitability.

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. Locate Premium Addons for KingComposer plugin
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'premium-addons-for-kingcomposer' or similar variant. Alternatively, view the installed plugins list in WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder or listing is found in the WordPress installation.
  2. Determine the installed plugin version
    Open the main plugin PHP file (typically premium-addons-for-kingcomposer.php) and locate the plugin header comment which contains the Version field. Alternatively, check the version constant defined in the plugin files.
    Affected if The plugin is installed and a version number is returned.
  3. Compare your version against affected releases
    Document the version number found. Research or consult vulnerability databases for CVE-2025-49036 to identify the specific vulnerable version range. Compare your installed version against this range.
    Affected if Your version falls within the documented vulnerable version range.
  4. Verify the plugin is active
    In WordPress admin, check if Premium Addons for KingComposer is activated. Alternatively, query the wp_options table for the active_plugins option to see if the plugin is loaded.
    Affected if The plugin is activated and running on the WordPress site.
  5. Identify accessible file inclusion endpoints
    Review the plugin source code for PHP include, require, include_once, or require_once statements that use unsanitized input variables (commonly $_GET, $_POST, or $_REQUEST parameters). Use a code search tool to grep for patterns like 'include($_' or 'require($_' within the plugin folder.
    Affected if File inclusion code that accepts dynamic path parameters without proper validation is found in the active plugin.

You are affected if Premium Addons for KingComposer is installed, active, and your version falls within the vulnerable range or contains the insecure file inclusion patterns described in CVE-2025-49036.

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

Upgrade to a patched version of Premium Addons for KingComposer. If no patch is available, implement input validation using allowlists for file paths and disable PHP execution in upload directories to limit exploitability.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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