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

CVE-2025-32921

HIGH · 7.5 CVSS v3.1 Published 2025-04-24
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 wpoperations Arrival arrival allows PHP Local File Inclusion.This issue affects Arrival: from n/a through <= 1.4.5.

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 PHP Local File Inclusion (LFI) vulnerability in the wpoperations Arrival WordPress plugin (versions through 1.4.5). The plugin fails to properly validate file paths in include/require statements, allowing attackers to potentially include arbitrary local PHP files and execute malicious code on the server.

MitigationUpdate the Arrival plugin to the latest patched version once released, or remove/disable the plugin if no patch is available. Until patched, consider restricting access to the plugin or monitoring for suspicious file inclusion attempts.

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. Verify if Arrival plugin is installed
    Check the WordPress plugins directory for the Arrival or wpoperations plugin folder. Common paths include /wp-content/plugins/arrival/ or /wp-content/plugins/wpoperations/. Look for a folder with either name.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Determine installed version
    Open the main plugin PHP file (typically plugin-name.php in the plugin root) and look for the version header comment or Version: field in the plugin metadata at the top of the file.
    Affected if The version listed is 1.4.5 or any earlier version (the vulnerability affects versions through 1.4.5)
  3. Confirm plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or query the WordPress database wp_options table for the active_plugins option to check if the plugin is enabled.
    Affected if The Arrival or wpoperations plugin shows as Active in the WordPress admin or is listed in active_plugins
  4. Inspect for vulnerable include/require patterns
    Examine the plugin PHP files for include(), require(), include_once(), or require_once() statements that use unsanitized variables in the file path, such as include($_GET['file']) or include($some_variable). Search the plugin directory for these patterns.
    Affected if Any PHP file in the plugin contains include/require statements that incorporate user-controlled input without proper validation

You are affected if the Arrival plugin (versions 1.4.5 or earlier) is installed and active, and contains vulnerable file inclusion code that uses unsanitized input in include/require statements.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Arrival plugin to the latest patched version once released, or remove/disable the plugin if no patch is available. Until patched, consider restricting access to the plugin or monitoring for suspicious file inclusion attempts.

Recommended fix Moderate confidence

Arrival plugin version > 1.4.5 (latest available version in WordPress plugin repository)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Arrival' plugin by wpoperations
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version (greater than 1.4.5)
  5. 5. Verify the update completed successfully
  6. 6. Test that the plugin functionality remains intact

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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