CVE-2025-68984
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 thembay Puca puca allows PHP Local File Inclusion.This issue affects Puca: from n/a through <= 2.6.39.
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 confidencePHP Local File Inclusion vulnerability in the Puca theme allows attackers to include arbitrary local PHP files via unsanitized input in include/require statements, potentially leading to remote code execution if attacker-controlled files can be placed on the server or sensitive files accessed.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Puca theme is installedCheck your WordPress or PHP application's theme directory for the presence of the 'puca' theme folder. Common paths include /wp-content/themes/puca/ or your application's themes directory.Affected if The puca theme folder exists in your themes directory
-
Identify Puca theme versionLocate the style.css or theme.json file within the puca theme folder and read the Version: header field, or check for a version.php/changelog file.Affected if The installed version matches or precedes the vulnerable version range for CVE-2025-68984
-
Inspect file inclusion code for unsanitized inputSearch the theme's PHP files (particularly in include/require statements) for patterns like include($_GET[...]) or require($_POST[...]) without sanitization functions such as basename() or realpath(). Use grep: grep -rn '\$_GET\|\$_POST\|\$_REQUEST' --include='*.php' in the theme directory.Affected if Code contains include/require statements directly using superglobal input without validation
-
Verify PHP allow_url_include settingCheck your php.ini file for the allow_url_include directive, or create a PHP info page (<?php phpinfo(); ?)) and search for 'allow_url_include'.Affected if allow_url_include is set to On (1), which enables remote file inclusion in addition to local file inclusion
-
Check for file upload functionalityExamine if the application or any installed plugins allow file uploads to writable directories (typically wp-content/uploads/). Look for upload forms or media library functionality.Affected if File upload capability exists and uploads are placed in a web-accessible directory where attacker-controlled PHP files could be stored
You are affected if the Puca theme is installed, contains vulnerable unsanitized file inclusion code, and the environment permits file uploads to web-accessible paths or has allow_url_include enabled.
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.
From vendor dataUpgrade to patched version when available; implement strict whitelist-based input validation on all file inclusion paths and disable allow_url_include in php.ini as defense-in-depth.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68984 — 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-68984 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