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

CVE-2025-10269

HIGH · 7.5 CVSS v3.1 Published 2025-09-12
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
The Spirit Framework plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.2.13. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 · high confidence

The Spirit Framework WordPress plugin versions up to 1.2.13 contains a Local File Inclusion (LFI) vulnerability. Authenticated attackers with Subscriber-level permissions can manipulate file inclusion parameters to include and execute arbitrary .php files on the server, achieving remote code execution.

MitigationUpdate the Spirit Framework plugin to version 1.2.14 or later. If no patched version is available, disable the plugin immediately. Additionally, implement web application firewall rules to block directory traversal patterns (e.g., ../) in request parameters.

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 Spirit Framework plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and search for 'Spirit Framework' or 'spirit-framework'
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In the plugins list, locate the Spirit Framework plugin and note the version number displayed under the plugin name
    Affected if Version is 1.2.13 or lower (the vulnerable range)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Spirit Framework plugin shows as 'Active'
    Affected if Plugin status is Active - an active vulnerable plugin can be exploited
  4. Check for subscriber-level user accounts
    Navigate to WordPress admin > Users and review user roles. Note any accounts with 'Subscriber' role
    Affected if Subscriber-level accounts exist - these can potentially exploit the LFI flaw if the vulnerable plugin is in use

If the Spirit Framework plugin is installed, active, and at version 1.2.13 or lower, the environment is affected by this LFI vulnerability.

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 Spirit Framework plugin to version 1.2.14 or later. If no patched version is available, disable the plugin immediately. Additionally, implement web application firewall rules to block directory traversal patterns (e.g., ../) in request parameters.

Recommended fix Moderate confidence

Spirit Framework plugin version 1.2.14 or latest stable release

  1. Check current version of the Spirit Framework plugin in WordPress admin under Plugins > Installed Plugins
  2. If the installed version is 1.2.13 or lower, navigate to Dashboard > Updates or Plugins > Add New > Upload Plugin
  3. Update the Spirit Framework plugin to the latest available version (1.2.14 or higher)
  4. After updating, verify the new version number reflects the update
  5. Test that the plugin functionality still works as expected
  6. Ensure no arbitrary .php files can be included via the vulnerable parameter (the exact parameter should be identified from the plugin's code or WordPress security advisories)

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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