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

CVE-2025-3703

HIGH · 7.5 CVSS v3.1 Published 2025-08-14
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 wipeoutmedia CSS & JavaScript Toolbox css-javascript-toolbox allows PHP Local File Inclusion.This issue affects CSS & JavaScript Toolbox: from n/a through < 12.0.3.

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 CSS & JavaScript Toolbox plugin allows unauthenticated remote attackers to include and execute arbitrary PHP files on the server by manipulating file path parameters in include/require statements.

MitigationUpdate CSS & JavaScript Toolbox plugin to version 12.0.3 or later to patch the file inclusion vulnerability; if immediate update is not possible, disable the plugin until patched.

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 CSS & JavaScript Toolbox plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CSS & JavaScript Toolbox' in the list, or check the /wp-content/plugins/ directory for the css-javascript-toolbox folder
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find CSS & JavaScript Toolbox, and view the version number displayed below the plugin name
    Affected if The installed version is lower than 12.0.3 (vulnerable versions are those prior to the 12.0.3 patch)
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that CSS & JavaScript Toolbox shows 'Active' status under the plugin name
    Affected if The plugin is active - the LFI vulnerability requires the plugin code to be executing to allow file inclusion via manipulated parameters
  4. Identify vulnerable parameter usage
    Review server access logs for suspicious requests containing '../' path traversal sequences or file path parameters targeting include/require statements (e.g., ?file=, ?path=, ?page=)
    Affected if Unusual file inclusion patterns appear in logs targeting the plugin's PHP files

A WordPress site is affected if CSS & JavaScript Toolbox plugin version is below 12.0.3 and the plugin is active, allowing unauthenticated attackers to manipulate file path parameters for local file inclusion.

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 CSS & JavaScript Toolbox plugin to version 12.0.3 or later to patch the file inclusion vulnerability; if immediate update is not possible, disable the plugin until patched.

Recommended fix Moderate confidence

CSS & JavaScript Toolbox version 12.0.3

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'CSS & JavaScript Toolbox' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 12.0.3
  5. 5. Alternatively, manually download version 12.0.3 from the WordPress plugin repository or the vendor
  6. 6. Deactivate the current plugin version if update fails, then install the new version
  7. 7. After updating, verify the plugin is functioning correctly

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-3703 — 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-3703 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