CurlyWordPress extension · Qodeinteractive
CVE-2025-67936
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 Mikado-Themes Curly curly allows PHP Local File Inclusion.This issue affects Curly: from n/a through < 3.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 · high confidenceThis is a Local File Inclusion (LFI) vulnerability in the Mikado-Themes Curly theme (versions before 3.3). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file path parameters to include arbitrary PHP files from the server, potentially leading to remote code execution.
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
CurlyWordPress extension
< 3.3CVSS 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.
-
Identify Curly theme installationLocate the Curly theme files in your WordPress or PHP application's wp-content/themes or themes directory. Look for folders named 'curly', 'Qodeinteractive-Curly', or similar.Affected if The Curly theme by Qodeinteractive is present in the themes directory.
-
Determine installed theme versionOpen the style.css file within the Curly theme folder and locate the 'Version:' comment in the file header, or check for a version.php file or theme.json that contains version information.Affected if The version number found is less than 3.3 (e.g., 3.2, 3.1, 3.0, etc.).
-
Locate PHP file inclusion codeSearch the Curly theme folder for PHP files containing include, include_once, require, or require_once statements that use variables or request parameters in the file path (e.g., include($file), include($_GET['page']), require($path)).Affected if Dynamic file inclusion statements that accept user-controlled input are found in the theme's PHP files.
-
Identify accessible file path parametersReview the identified vulnerable PHP files to determine which URL parameters (GET/POST) control the file path in include/require statements. Test accessing those parameters on the frontend.Affected if URL parameters that control file inclusion are accessible and can be manipulated through HTTP requests.
-
Verify the vulnerability is exploitableAttempt a benign LFI test by including a known file (e.g., a configuration file accessible on the server) through the suspected vulnerable parameter, observing whether the file content is returned.Affected if Arbitrary files from the server can be included and their contents displayed through the vulnerable parameter.
A user is affected if the Curly theme version is below 3.3 AND dynamic file inclusion code using controllable parameters exists and is accessible on their site.
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 · scoped3.3
Upgrade the Curly theme to version 3.3 or later. If immediate upgrade is not possible, implement strict input validation on all file inclusion parameters to ensure only whitelisted files can be included, and ensure PHP configuration has allow_url_include disabled.
3.3
- 1. Check the current installed version of the Curly theme in your WordPress installation
- 2. Create a complete backup of your WordPress site (database and files)
- 3. Download the Curly theme version 3.3 or later from the official source (Mikado-Themes/ThemeForest)
- 4. Navigate to Appearance > Themes in WordPress admin and activate a different theme temporarily
- 5. Delete the vulnerable Curly theme installation
- 6. Upload and install the new Curly theme version 3.3 or later
- 7. Reactivate the Curly theme and verify all functionality works correctly
- 8. Clear any caching mechanisms and test that the LFI vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Curly
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67936 — 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-67936 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