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

CVE-2025-12851

HIGH · 8.1 CVSS v3.1 Published 2025-12-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The My auctions allegro plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.6.32 via the 'controller' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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

The My auctions allegro WordPress plugin versions up to 3.6.32 is vulnerable to unauthenticated Local File Inclusion via the 'controller' parameter. Attackers can manipulate this parameter to include arbitrary files from the server, enabling PHP code execution and potentially bypassing access controls to obtain sensitive data or achieve RCE.

MitigationUpdate the plugin to version 3.6.33 or later which contains the patch. If unable to update immediately, consider disabling the plugin or implementing Web Application Firewall rules to block requests with traversal patterns in the controller parameter.

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

CVSS:3.1/AV:N/AC:H/PR:N/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 My auctions allegro plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'My auctions allegro' or 'Moje aukcje allegro'. Alternatively, check the plugin directory wp-content/plugins/ for a folder containing 'allegro' in the name.
    Affected if The plugin is present on the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the My auctions allegro plugin to view its version number. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comments.
    Affected if The version is 3.6.32 or below, or if no version is displayed (indicating it may be an unmodified version from before updates)
  3. Identify the vulnerable endpoint
    Locate the PHP file that handles the 'controller' parameter. This is typically in the plugin's main directory or an ajax handler. Look for code that uses include(), include_once(), require(), or require_once() with the controller parameter without proper sanitization.
    Affected if The plugin processes a 'controller' parameter in PHP code that performs file inclusion without sanitizing directory traversal sequences (../) or null bytes
  4. Test for LFI vulnerability (safe check)
    If you have authorization, review the plugin source code for the file inclusion logic. The vulnerable code will accept the controller parameter and use it in an include statement without validation. Search for patterns like 'include($_GET["controller"]' or similar dynamic file inclusion.
    Affected if The code allows arbitrary file paths via the controller parameter without validation, enabling directory traversal attacks

A WordPress site is affected if it has the My auctions allegro plugin installed at version 3.6.32 or below and the plugin processes a 'controller' parameter in file inclusion operations without proper sanitization.

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 plugin to version 3.6.33 or later which contains the patch. If unable to update immediately, consider disabling the plugin or implementing Web Application Firewall rules to block requests with traversal patterns in the controller parameter.

Recommended fix High confidence

Version 3.6.33 or latest available version of My auctions allegro plugin

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'My auctions allegro' plugin
  4. Click 'Update now' if an update is available, or manually update to the latest version
  5. Verify the plugin is updated to version 3.6.33 or later

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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