dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-63062

HIGH · 7.5 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AndonDesign UDesign Core u-design-core allows PHP Local File Inclusion.This issue affects UDesign Core: from n/a through <= 4.14.0.

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 confidence

UDesign Core plugin for WordPress contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in include/require statements. This allows attackers to read sensitive local files on the server by manipulating file path parameters, potentially exposing configuration files, credentials, or other sensitive data.

MitigationUpdate to the latest patched version of UDesign Core; if unavailable, disable the plugin and implement web application firewall rules to block directory traversal patterns in URL 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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify UDesign Core plugin is installed
    Check your WordPress site's wp-content/plugins/udesign-core directory exists, or look for 'UDesign Core' in the Plugins admin page
    Affected if The plugin directory exists or the plugin appears in WordPress admin plugins list
  2. Identify installed UDesign Core version
    Open the main plugin file (typically udesign-core.php) in wp-content/plugins/udesign-core/ and locate the version definition in the plugin header comment, or check readme.txt for the 'Stable tag' entry
    Affected if The version number found is lower than the patched version or cannot be determined (indicating outdated installation)
  3. Locate file inclusion functionality
    Review plugin source code for PHP include(), require(), or similar functions that accept user-controlled parameters, typically in files handling templates, partials, or dynamic content loading
    Affected if Code contains include/require statements using parameters from $_GET, $_POST, or similar superglobals without proper validation
  4. Inspect for missing input validation
    Examine the file inclusion code identified in step 3 for sanitization functions (such as realpath(), basename(), or allowlist checks) applied to the file path parameter before use in include/require
    Affected if The file path parameter is used directly in include/require without validation, or validation can be bypassed using directory traversal sequences like ../
  5. Test for directory traversal vulnerability
    If the vulnerable parameter is identified, attempt a controlled test request with a path like ../../../wp-config.php to see if the application attempts to include files outside the intended directory
    Affected if The server responds to traversal patterns without blocking or returns errors indicating file access attempts

A user is affected if UDesign Core plugin is installed with an unpatched version and contains file inclusion functionality that lacks proper input validation on file path parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of UDesign Core; if unavailable, disable the plugin and implement web application firewall rules to block directory traversal patterns in URL parameters.

Recommended fix Moderate confidence

UDesign Core version > 4.14.0 (any version newer than 4.14.0 that includes the security fix)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to WordPress admin dashboard > Appearance > Themes
  3. 3. Deactivate the current UDesign Core theme
  4. 4. Delete the current UDesign Core theme installation
  5. 5. Download the latest version of UDesign Core from a trusted source (the theme developer's official website or repository)
  6. 6. Upload and install the new version of UDesign Core theme
  7. 7. Reactivate the UDesign Core theme
  8. 8. Verify the website frontend and admin functionality work correctly
Caveat Theme updates may change design/layout settings - review and reapply custom configurations as needed after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-63062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-63062 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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