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

CVE-2025-68560

HIGH · 7.5 CVSS v3.1 Published 2025-12-23
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 CodexThemes TheGem Theme Elements (for Elementor) thegem-elements-elementor.This issue affects TheGem Theme Elements (for Elementor): from n/a through <= 5.10.5.1.

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

A Remote File Inclusion (RFI) vulnerability in TheGem Theme Elements for Elementor allows attackers to include arbitrary remote files via PHP include/require statements due to improper control of filename parameters. This can lead to remote code execution on the affected server.

MitigationUpdate TheGem Theme Elements to the latest patched version beyond 5.10.5.1. If patching is not immediately possible, review and restrict any include/require statements to validate and sanitize file path inputs, and consider disabling the affected component until patched.

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. Identify if TheGem Theme Elements for Elementor is installed
    Check your WordPress plugins directory for 'thegem-elements' folder, or look for TheGem theme files in wp-content/themes/thegem. Alternatively, check your WordPress admin dashboard under Plugins or Theme section for TheGem Theme Elements.
    Affected if TheGem Theme Elements for Elementor plugin or theme is not found on the system.
  2. Determine the installed version of TheGem Theme Elements
    If using the plugin: check the plugin file header in wp-content/plugins/thegem-elements/elements.php or the main plugin file for 'Version:' tag. If using the theme: check style.css in wp-content/themes/thegem for 'Version:' in the header comments.
    Affected if The version is 5.10.5.1 or earlier (any version up to and including 5.10.5.1 is affected).
  3. Locate the vulnerable element/component
    Search the plugin/theme directory for files that contain PHP include, require, include_once, or require_once statements that process file path parameters. Look for patterns like $_GET['file'], $_REQUEST['path'], or similar user-controlled filename variables being passed to include/require functions.
    Affected if Files containing include/require statements with unsanitized file path parameters are found in the TheGem Elements directory.
  4. Identify the specific vulnerable endpoint
    Examine the PHP files identified in the previous step to determine the URL endpoint or query parameter that triggers the include/require. Common patterns include parameters named 'file', 'path', 'template', or 'load'.
    Affected if A callable endpoint exists that accepts a remote URL or file path via GET/POST parameters and passes it directly to include/require without validation.

If TheGem Theme Elements for Elementor is installed and the version is 5.10.5.1 or earlier with an accessible include/require endpoint using unsanitized file path parameters, the environment is vulnerable to CVE-2025-68560.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update TheGem Theme Elements to the latest patched version beyond 5.10.5.1. If patching is not immediately possible, review and restrict any include/require statements to validate and sanitize file path inputs, and consider disabling the affected component until patched.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68560 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68560 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