CVE-2025-48298
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Benjamin Denis SEOPress for MainWP seopress-for-mainwp allows PHP Local File Inclusion.This issue affects SEOPress for MainWP: from n/a through <= 1.4.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability in the SEOPress for MainWP plugin (versions <= 1.4) allows attackers to include arbitrary PHP files from the local server due to improper control of filenames in include/require statements. This can lead to remote code execution if the attacker can manipulate which files get included.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SEOPress for MainWP plugin installation and versionCheck the plugin directory or WordPress admin panel for the installed version of SEOPress for MainWP. Look in wp-content/plugins/ for a directory named seopress-mainwp or similar, and examine the main plugin file for the version number.Affected if The plugin is installed and the version is 1.4 or lower.
-
Verify the plugin is active on the WordPress siteCheck the WordPress database wp_options table for active_plugins entry, or inspect wp-content/advanced-cache.php to determine if the SEOPress for MainWP plugin is currently enabled.Affected if The plugin is active and running.
-
Locate the vulnerable file inclusion codeSearch the plugin files for include, require, include_once, or require_once statements that use variables or request parameters without sanitization. Focus on files that handle file path operations.Affected if The plugin contains include/require statements using unsanitized user input for file paths.
-
Identify accessible entry points for file inclusionReview plugin PHP files for parameters (such as 'page', 'file', 'path', or similar) that control which files get included. Check if these parameters can be manipulated via HTTP requests.Affected if User-controlled parameters can be manipulated to include arbitrary local PHP files.
-
Confirm the LFI vulnerability is exploitableTest whether the identified vulnerable endpoint accepts path traversal sequences (such as ../../) and can include files outside the intended directory.Affected if The file inclusion mechanism allows path traversal and includes files based on attacker-controlled input.
A site is affected if SEOPress for MainWP version 1.4 or lower is installed, active, and contains the vulnerable file inclusion code that can be triggered via HTTP parameters to achieve local file inclusion.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of SEOPress for MainWP once released. Until then, disable the plugin or deploy a WAF to block malicious file inclusion requests.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48298 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48298 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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