LekkerWordPress extension · Qodeinteractive
CVE-2025-69034
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 Lekker lekker allows PHP Local File Inclusion.This issue affects Lekker: from n/a through <= 1.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 confidenceLocal File Inclusion (LFI) vulnerability in Mikado-Themes Lekker (version <=1.8) where improper control of filenames in PHP include/require statements allows attackers to include and execute arbitrary PHP files from the local 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
LekkerWordPress extension
<= 1.8CVSS 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.
-
Confirm Lekker theme installation and versionLocate the Lekker theme directory (typically wp-content/themes/lekker/) and check the style.css header for the Version declaration, or check functions.php for a version constantAffected if The theme is installed and the version number is 1.8 or lower
-
Identify include/require statements using variablesSearch PHP files in the Lekker theme directory for patterns like 'include($', 'require($', 'include_once($', or 'require_once($' where variables are used directly in include/require statementsAffected if Any PHP file contains include/require statements that use unsanitized variable inputs
-
Check for user-controlled file path parametersReview the identified include/require files to determine if the variables passed to them come from request parameters (GET, POST, COOKIE) without sanitizationAffected if File path variables are derived from user input without validation or path restriction
-
Verify the vulnerable code is accessibleConfirm the vulnerable PHP files are accessible via web requests by testing the suspected parameter injection points (for example, by attempting a benign inclusion of a known local file)Affected if The LFI-prone code can be triggered through HTTP requests to the site
You are affected if Lekker theme version is 1.8 or lower AND your site has PHP include/require code that uses user-supplied input in an unsafe manner, allowing arbitrary file inclusion from the local filesystem.
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 a patched Lekker theme version that implements proper input validation and sanitization on file path parameters used in include/require statements, restricting inclusion to expected/whitelisted paths.
Fix this in Lekker
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-69034 — 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-69034 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