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

CVE-2026-22464

HIGH · 7.5 CVSS v3.1 Published 2026-01-22
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 wphocus My auctions allegro my-auctions-allegro-free-edition allows PHP Local File Inclusion.This issue affects My auctions allegro: from n/a through <= 3.6.33.

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 wphocus My auctions allegro WordPress plugin (versions <= 3.6.33) where user-supplied input is improperly validated before being used in include/require statements, potentially allowing attackers to read sensitive local files from the server filesystem.

MitigationUpgrade to a patched version of the My auctions allegro plugin. If no patched version is available, disable the plugin. Additionally, implement web application firewall rules to block directory traversal patterns (e.g., ../../../) in incoming requests.

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 if My auctions allegro plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder named 'my-auctions-allegro' or similar wphocus auction-related plugin
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Determine the installed plugin version
    Check the plugin header comment in the main PHP file (usually my-auctions-allegro.php) for the Version field, or view the version in the WordPress plugins admin page
    Affected if The reported version is 3.6.33 or lower
  3. Confirm the plugin is active
    Check the WordPress database wp_options table for option_name containing 'active_plugins', or view the Plugins admin page status
    Affected if The plugin appears in the list of active plugins
  4. Identify PHP files handling include/require statements
    Search the plugin directory for PHP files containing include, include_once, require, or require_once statements, particularly looking for variables used in these statements
    Affected if The plugin contains include/require statements that use variables without sanitization
  5. Check for accessible vulnerable endpoints
    Review the plugin's router or main entry points to identify parameters that could control the include/require paths (common parameter names: file, page, template, path, include)
    Affected if User-supplied parameters can be passed to include/require functions without validation
  6. Review web server access logs for exploitation attempts
    Search access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests containing directory traversal patterns (../) targeting the plugin's PHP files
    Affected if Logs show requests with traversal patterns pointing to plugin files

You are affected if the My auctions allegro plugin is installed, active, and running version 3.6.33 or lower, with vulnerable include/require code accessible via URL parameters.

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 the My auctions allegro plugin. If no patched version is available, disable the plugin. Additionally, implement web application firewall rules to block directory traversal patterns (e.g., ../../../) in incoming requests.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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