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

CVE-2025-22279

HIGH · 7.5 CVSS v3.1 Published 2025-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 Crocoblock JetCompareWishlist jet-compare-wishlist allows PHP Local File Inclusion.This issue affects JetCompareWishlist: from n/a through <= 1.5.9.

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

A PHP Local File Inclusion (LFI) vulnerability in the Crocoblock JetCompareWishlist plugin (versions <= 1.5.9) allows attackers to manipulate filename parameters in include/require statements, potentially executing arbitrary PHP code or reading sensitive local files on the server.

MitigationUpgrade JetCompareWishlist to the latest patched version. If no patch is available, disable the plugin until a fix is released, or audit the plugin code to implement proper input validation on file inclusion functions.

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

CVSS:3.1/AV:N/AC:H/PR:L/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 JetCompareWishlist plugin is installed
    Navigate to WordPress admin > Plugins and look for 'JetCompareWishlist' by Crocoblock in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on JetCompareWishlist to view the plugin details and version number
    Affected if The displayed version is 1.5.9 or lower (any version <= 1.5.9)
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that JetCompareWishlist shows as 'Active' rather than 'Inactive'
    Affected if The plugin status is Active and the version is <= 1.5.9
  4. Inspect server access logs for LFI attempt patterns
    Review web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests containing '../', '..\', or file path references targeting include/require parameters
    Affected if Suspicious LFI-style requests are found in logs targeting the JetCompareWishlist plugin
  5. Check for the vulnerable file inclusion endpoint
    Examine the JetCompareWishlist plugin files (typically in wp-content/plugins/jet-compare-wishlist/) for direct file inclusion calls using $_GET or $_REQUEST parameters without proper sanitization
    Affected if Unsanitized file inclusion code is found in the plugin files

A user is affected if the JetCompareWishlist plugin is installed, active, and running version 1.5.9 or lower.

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

Upgrade JetCompareWishlist to the latest patched version. If no patch is available, disable the plugin until a fix is released, or audit the plugin code to implement proper input validation on file inclusion functions.

Recommended fix Moderate confidence

Latest available version of JetCompareWishlist (version > 1.5.9)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate JetCompareWishlist by Crocoblock
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. After updating, verify the plugin version is newer than 1.5.9
  6. 6. Test that the JetCompareWishlist functionality works correctly after the update
Caveat Review the plugin changelog for any breaking changes between your current version and the new version before updating in production

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.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-22279 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22279 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