SmilepureWordPress extension · Thememove
CVE-2025-58958
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeMove SmilePure smilepure allows PHP Local File Inclusion.This issue affects SmilePure: from n/a through < 1.8.5.
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 confidenceThe SmilePure theme by ThemeMove contains a PHP Local File Inclusion (LFI) vulnerability in versions before 1.8.5. The vulnerability stems from improper control of filenames used in PHP include/require statements, allowing an attacker to manipulate the file path and include arbitrary PHP files from the local server filesystem.
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
SmilepureWordPress extension
< 1.8.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate SmilePure theme installationSearch your web server's themes directory (commonly wp-content/themes/ for WordPress or similar paths for other platforms) for a folder named 'smilepure' or 'smilepure' by ThemeMove.Affected if The SmilePure theme folder exists on the server.
-
Determine installed versionOpen the theme's main style.css file or version.php file (typically found in the theme root directory) and locate the version declaration. Compare this version number to the affected range of < 1.8.5.Affected if The reported version is below 1.8.5.
-
Identify PHP include/require usageSearch the theme's PHP files for include, include_once, require, or require_once statements that use variables or parameters in the file path without proper sanitization. Look for patterns like 'include($var)' or 'require($_GET[...])' within theme files.Affected if PHP files contain dynamic file inclusion using unsanitized user input.
-
Audit for suspicious request patternsReview web server access logs for requests to theme PHP files that contain directory traversal patterns (such as ../ or absolute file paths) in query parameters, especially targeting known include/require endpoints.Affected if Logs show requests with traversal patterns sent to theme files.
You are affected if the SmilePure theme is installed with a version below 1.8.5 and contains PHP files with dynamic file inclusion that could accept user-supplied file paths.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.8.5
Update SmilePure to version 1.8.5 or later. If immediate patching is not possible, restrict web server access to vulnerable theme files and audit for any signs of exploitation.
Smilepure 1.8.5
- Backup your WordPress site before making any changes
- Update the Smilepure theme to version 1.8.5 or later through WordPress admin (Appearance > Themes) or your theme distribution source
- After updating, verify the theme version shows 1.8.5 or higher in WordPress admin under Appearance > Themes
- Clear any caching layers (plugin cache, CDN cache, server-side cache) to ensure the patched files are served
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Smilepure
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58958 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58958 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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