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

CVE-2025-48338

HIGH · 7.5 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Kevon Adonis WP Abstracts wp-abstracts-manuscripts-manager allows PHP Local File Inclusion.This issue affects WP Abstracts: from n/a through <= 2.7.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 · moderate confidence

A PHP Local File Inclusion vulnerability exists in the WP Abstracts plugin (wp-abstracts-manuscripts-manager component) versions through 2.7.4. The vulnerability allows attackers to include arbitrary local PHP files due to improper control of filenames in include/require statements, potentially leading to remote code execution.

MitigationUpdate to a patched version of WP Abstracts if available. If no patch exists, disable the plugin immediately. Additionally, disable allow_url_fopen and allow_url_include in php.ini as defense-in-depth, and ensure proper input validation is implemented on all file inclusion operations.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the WP Abstracts plugin installation directory
    Check your WordPress plugins folder (typically wp-content/plugins/) for a folder named 'wp-abstracts', 'wp-abstracts-manuscripts-manager', or similar.
    Affected if The plugin folder is present in the plugins directory
  2. Identify the installed WP Abstracts version
    Open the main plugin file (usually wp-abstracts.php or index.php) in the plugin folder and locate the version declaration in the plugin header comment, or check the readme.txt file for the version field.
    Affected if The version number displayed is 2.7.4 or lower
  3. Verify the wp-abstracts-manuscripts-manager component exists
    Check inside the WP Abstracts plugin folder for a subfolder or file named 'wp-abstracts-manuscripts-manager', 'manuscripts-manager', or containing 'include' files that handle file inclusions.
    Affected if The manuscripts-manager component is present in the plugin installation
  4. Review PHP file inclusion patterns in the plugin code
    Search the plugin source files for dynamic include, require, include_once, or require_once statements that use variables without proper sanitization (e.g., include($some_variable); or require($_GET['file']);).
    Affected if Dynamic file inclusion code using unsanitized user input is found in the plugin files
  5. Check for suspicious access patterns in web server logs
    Review Apache or Nginx access logs for requests to the WP Abstracts plugin that contain path traversal sequences (e.g., ../../) or attempts to include PHP files from non-standard paths.
    Affected if Log entries show LFI attempts targeting the WP Abstracts plugin endpoints
  6. Confirm the plugin is actively loaded on the site
    Check WordPress active plugins configuration or inspect the site's frontend to verify WP Abstracts is enabled and processing requests.
    Affected if WP Abstracts is active and handling manuscript-related requests on the website

The environment is affected if WP Abstracts plugin version 2.7.4 or lower is installed with the manuscripts-manager component present and actively processing requests.

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 to a patched version of WP Abstracts if available. If no patch exists, disable the plugin immediately. Additionally, disable allow_url_fopen and allow_url_include in php.ini as defense-in-depth, and ensure proper input validation is implemented on all file inclusion operations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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