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

CVE-2025-30835

HIGH · 7.5 CVSS v3.1 Published 2025-03-31
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 Bastien Ho Accounting for WooCommerce accounting-for-woocommerce allows PHP Local File Inclusion.This issue affects Accounting for WooCommerce: from n/a through <= 1.6.8.

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

The Accounting for WooCommerce plugin through version 1.6.8 contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is used in include/require statements without proper validation. This allows remote attackers to include arbitrary PHP files, potentially leading to remote code execution on the server.

MitigationUpdate to a patched version of the plugin when available. Until then, disable the plugin or restrict web server access to prevent exploitation of the vulnerable file inclusion mechanism.

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 Accounting for WooCommerce plugin is installed
    Locate the plugin directory in your WordPress installation under wp-content/plugins/ and confirm the accounting-for-woocommerce folder exists
    Affected if The plugin folder is present on the server
  2. Determine installed plugin version
    Open the main plugin file (usually accounting-for-woocommerce.php) or the readme.txt file in the plugin directory and locate the Version header
    Affected if The reported version is 1.6.8 or lower
  3. Compare version against affected range
    Check the version found against the affected range: any version 1.6.8 or below is considered vulnerable
    Affected if The installed version is 1.6.8 or any version number lower than 1.6.8
  4. Identify the LFI entry point
    Search the plugin PHP files for include, require, include_once, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without sanitization (common patterns: include($_GET['file']), require($var), etc.)
    Affected if Any include/require statements using unsanitized user input are found in the plugin code
  5. Confirm exposure of vulnerable endpoint
    Check if the file containing the vulnerable include/require logic is directly accessible via the web (not protected by WordPress admin checks or authentication)
    Affected if The vulnerable file can be accessed directly via HTTP without authentication

Your environment is affected if the Accounting for WooCommerce plugin is installed with version 1.6.8 or lower and contains unprotected include/require statements using user-supplied input.

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 to a patched version of the plugin when available. Until then, disable the plugin or restrict web server access to prevent exploitation of the vulnerable file inclusion mechanism.

Recommended fix Moderate confidence

Upgrade to the latest version of Accounting for WooCommerce (version > 1.6.8)

  1. Navigate to the WordPress admin dashboard for the site using the Accounting for WooCommerce plugin
  2. Go to Plugins > Installed Plugins
  3. Locate Accounting for WooCommerce in the plugin list
  4. Check if the current version is 1.6.8 or lower (vulnerable)
  5. If vulnerable, click 'Update Now' to install the latest patched version, or manually download the updated plugin from the official WordPress plugin repository
  6. After updating, verify the new version number reflects the patch

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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