CVE-2025-69141
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 · uneditedUnauthenticated Local File Inclusion in Kelly Young <= 1.1.0 versions.
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 confidenceUnauthenticated Local File Inclusion (LFI) vulnerability in Kelly Young plugin/theme versions 1.1.0 and earlier allows remote, unauthenticated attackers to read arbitrary files on the server file system by manipulating path traversal sequences in vulnerable parameters.
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
- 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 Kelly Young versionLocate the plugin/theme version file - typically in the main PHP file header comments, readme.txt, or version constant. Common paths: wp-content/plugins/kelly-young/ or wp-content/themes/kelly-young/Affected if The installed version is 1.1.0 or earlier, or if the version cannot be determined (treat as affected)
-
Confirm plugin/theme is activeCheck if the Kelly Young plugin or theme is installed and enabled on the WordPress site. In WordPress admin, look at the Plugins or Themes page, or query the wp_options table for active_plugin/theme options.Affected if Kelly Young is installed and active - the vulnerability only affects the running component
-
Check for unauthenticated accessSince this is an unauthenticated LFI, verify the affected endpoints are accessible without authentication. Identify the vulnerable parameter(s) mentioned in the CVE - typically these accept file paths and are reachable via HTTP GET/POST requests without login.Affected if The vulnerable parameter endpoints are reachable without authentication (no login required)
-
Inspect code for path traversal logicExamine the PHP files in the Kelly Young plugin/theme for code that handles file inclusion or file reading operations. Look for functions like include, require, file_get_contents, readfile, or similar that use user-supplied input without proper sanitization. Search for patterns like $_GET, $_POST, or $_REQUEST used in file path operations.Affected if Code contains file read operations using unsanitized input from request parameters, allowing ../ sequences
-
Test configuration for path traversal blockingIf direct code inspection is not possible, check any WAF, web server config, or application-level filtering that may block path traversal patterns (../, ..\, or encoded variants). Review .htaccess rules or similar access controls.Affected if No path traversal filtering is in place and the vulnerable parameter is exposed
You are affected if Kelly Young version 1.1.0 or earlier is installed and active, and the vulnerable parameter accepting path traversal sequences is accessible without authentication.
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 Kelly Young to a version newer than 1.1.0 if available; if no patch exists, implement WAF rules blocking path traversal patterns (../, etc.) and consider temporarily disabling the affected component until remediation is available.
- 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-69141 — 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-69141 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