dbcve.org
WellspringWordPress extension · Qodeinteractive

CVE-2025-67934

HIGH · 8.1 CVSS v3.1 Published 2026-01-08
Fix available
A fix is available. Upgrade to 2.8 or later.
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes Wellspring wellspring allows PHP Local File Inclusion.This issue affects Wellspring: from n/a through < 2.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

PHP Local File Inclusion vulnerability in the Mikado-Themes Wellspring theme allows attackers to include arbitrary PHP files from the server via unsanitized user input in include/require statements. This can lead to disclosure of sensitive files, code execution, or further system compromise.

MitigationUpgrade Wellspring theme to version 2.8 or later. If immediate patching is not possible, implement strict input validation and whitelist-based filtering on all include/require statements, and ensure register_globals is disabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WellspringWordPress extension
Affected:< 2.8

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. Identify Wellspring theme installation
    Locate the theme directory on the web server. Wellspring is a Mikado Themes/Qodeinteractive theme, typically found in wp-content/themes/ on WordPress or in the themes folder of the application.
    Affected if The Wellspring theme by Qodeinteractive is present in the themes directory.
  2. Determine installed theme version
    Check the theme's version file, style.css header, or version.php. The version is commonly declared in the style.css file within the theme folder under 'Version:' or in a dedicated version.php file.
    Affected if The discovered version is below 2.8 (e.g., 2.7, 2.6, 1.x).
  3. Inspect include/require statements for user input
    Search theme PHP files for include, include_once, require, or require_once statements that use variables without sanitization. Look for patterns like 'include($var)', 'require($_GET["page"])', or similar where user-supplied data flows directly into these functions.
    Affected if The theme contains include/require statements that incorporate unsanitized user input (GET, POST, or COOKIE parameters).
  4. Verify register_globals configuration
    Check the PHP configuration file (php.ini) for the register_globals setting. This can also be verified via phpinfo() or by checking if the hosting environment allows global variable injection.
    Affected if register_globals is enabled, which increases the exploitability of LFI vulnerabilities.

You are affected if the Wellspring theme version is below 2.8 AND your application uses include/require statements with unsanitized user input in the theme files.

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
Upgrade available Upgrade to 2.8 or later
Fixed in 2.8
Interim mitigation

Upgrade Wellspring theme to version 2.8 or later. If immediate patching is not possible, implement strict input validation and whitelist-based filtering on all include/require statements, and ensure register_globals is disabled.

Recommended fix High confidence

Wellspring 2.8

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. If automatic updates are enabled, check for theme updates and update Wellspring to version 2.8
  4. Alternatively, manually upload and replace the Wellspring theme folder with version 2.8
  5. Verify the theme updated successfully by checking the theme version in Appearance > Themes
  6. Clear any caching plugins and server-side caches
  7. Test the website functionality to ensure the update did not break any features
Caveat Minor: Review theme settings after upgrade as some configuration changes may be needed; test customizations against the new version

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

Fix this in Wellspring Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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