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

CVE-2025-9991

HIGH · 8.1 CVSS v3.1 Published 2025-09-30
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 Tiny Bootstrap Elements Light plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.3.34 via the 'language' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php 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 .php 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 · moderate confidence

The Tiny Bootstrap Elements Light WordPress plugin (versions up to 4.3.34) is vulnerable to unauthenticated Local File Inclusion via the 'language' parameter. Attackers can include and execute arbitrary PHP files on the server, achieving remote code execution and potentially bypassing access controls or obtaining sensitive data.

MitigationUpdate the plugin to a version beyond 4.3.34 once a patch is released; if no patch is available, disable and remove the plugin. Consider deploying a WAF rule to block directory traversal patterns in the 'language' parameter as a temporary mitigation.

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. Locate the Tiny Bootstrap Elements Light plugin
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'tiny-bootstrap-elements' or similar. Read the main plugin file (usually plugin-name.php) to find the version declaration in the plugin header comment.
    Affected if The plugin folder exists in your plugins directory
  2. Identify the installed version
    In the plugin's main PHP file, look for a line like 'Version: x.x.x' in the file header comment. This is typically at the top of the main plugin PHP file.
    Affected if The version number is 4.3.34 or lower (for example, 4.3.34, 4.3.33, 4.3.0, etc.)
  3. Confirm the plugin is active
    Check your WordPress database wp_options table for the active_plugins option, or log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to verify the plugin status.
    Affected if The plugin shows as 'Active' in WordPress
  4. Check for signs of exploitation (optional)
    Review web server access logs for requests to pages using this plugin that contain 'language=../' or 'language=php://' directory traversal patterns in the query string.
    Affected if Suspicious directory traversal patterns appear in logs referencing the plugin

You are affected if the Tiny Bootstrap Elements Light plugin is installed, active, and the version is 4.3.34 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

Update the plugin to a version beyond 4.3.34 once a patch is released; if no patch is available, disable and remove the plugin. Consider deploying a WAF rule to block directory traversal patterns in the 'language' parameter as a temporary mitigation.

Recommended fix High confidence

Tiny Bootstrap Elements Light version 4.3.35 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Tiny Bootstrap Elements Light' in the plugin list
  4. Check the current version number to confirm it is 4.3.34 or lower
  5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/tiny-bootstrap-elements
  6. After updating, verify the plugin version shows 4.3.35 or higher in the Plugins list
  7. Confirm the site still functions correctly, particularly any pages using the plugin's shortcodes or elements
Caveat Minor WordPress plugin updates rarely introduce breaking changes; test on staging if possible

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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