dbcve.org
HealsoulWordPress extension · Thememove

CVE-2025-32309

HIGH · 8.1 CVSS v3.1 Published 2025-05-23
Fix available
A fix is available. Upgrade to 2.2.4 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 ThemeMove Healsoul healsoul allows PHP Local File Inclusion.This issue affects Healsoul: from n/a through <= 2.2.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 · moderate confidence

A Local File Inclusion (LFI) vulnerability in ThemeMove Healsoul theme allows attackers to manipulate filename parameters in PHP include/require statements to read arbitrary files on the server. The lack of proper input validation on user-controllable parameters enables path traversal attacks.

MitigationImplement strict whitelist-based input validation on all file inclusion parameters, use basename() to strip directory traversal sequences, and avoid using user input directly in include/require statements.

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
HealsoulWordPress extension
Affected:< 2.2.4

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 if Healsoul theme is installed
    Locate the theme directory - typically at wp-content/themes/healsoul/ in WordPress installations, or check for Healsoul theme files in the web root.
    Affected if The Healsoul theme directory exists on the server.
  2. Determine installed theme version
    Check the style.css file in the theme directory for the 'Version:' header, or look for a version.php/changelog.txt file within the theme.
    Affected if The reported version is less than 2.2.4.
  3. Locate PHP files with dynamic file inclusion
    Search theme PHP files for include(), require(), include_once(), or require_once() statements that reference variables in the filename parameter (e.g., include($_GET['...']).
    Affected if Files exist that use user-supplied input directly in include/require statements without sanitization.
  4. Inspect URL parameter handling for file paths
    Review PHP files that handle file inclusion for parameters that could accept file paths, particularly look for parameters used in include/require statements.
    Affected if The application accepts user-controlled parameters and passes them to file inclusion functions without validation.
  5. Check for path traversal vulnerability
    Test suspected parameters by attempting to include common paths (e.g., ../../../../etc/passwd) via GET/POST requests to see if arbitrary files can be read.
    Affected if The application returns file contents from paths outside the intended directory.

A user is affected if the Healsoul theme version is below 2.2.4 AND the theme exposes PHP files that use user input in include/require statements without proper validation.

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.2.4 or later
Fixed in 2.2.4
Interim mitigation

Implement strict whitelist-based input validation on all file inclusion parameters, use basename() to strip directory traversal sequences, and avoid using user input directly in include/require statements.

Recommended fix Moderate confidence

Healsoul version 2.2.4

  1. 1. Backup your entire WordPress site (database and files) before proceeding
  2. 2. Download Healsoul theme version 2.2.4 from the official ThemeMove source or your purchase account
  3. 3. Navigate to WordPress Admin Dashboard > Appearance > Themes
  4. 4. Activate a different theme temporarily (e.g., a default WordPress theme)
  5. 5. Delete the existing Healsoul theme
  6. 6. Upload and install Healsoul version 2.2.4
  7. 7. Activate Healsoul version 2.2.4
  8. 8. Verify the theme is functioning correctly and reapply any custom settings if needed

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

Fix this in Healsoul 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 the upgrade done

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