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

CVE-2025-68510

HIGH · 8.1 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 ThemeGoods Photography photography allows PHP Local File Inclusion.This issue affects Photography: from n/a through < 7.7.5.

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 · high confidence

A PHP Local File Inclusion vulnerability exists in ThemeGoods Photography theme (versions before 7.7.5) due to improper control of filenames in include/require statements. This allows attackers to include arbitrary PHP files from the server, potentially leading to remote code execution.

MitigationUpdate ThemeGoods Photography theme to version 7.7.5 or later. If immediate update is not possible, implement input validation and web application firewall rules to block directory traversal patterns in request 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 checks

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

  1. Locate ThemeGoods Photography theme installation
    Check your WordPress themes directory (wp-content/themes/) for a folder named 'photography' or similar theme folder from ThemeGoods. Identify the theme's main style.css file which contains the theme metadata.
    Affected if The theme folder is present in the themes directory
  2. Check installed theme version
    Open the theme's style.css file and look for the 'Version:' declaration in the theme header comment at the top of the file. Alternatively, check theme.json or functions.php for a version constant.
    Affected if The version number is lower than 7.7.5 (e.g., 7.7.4, 7.6.x, etc.)
  3. Inspect include/require statements for the vulnerability pattern
    Search theme PHP files (especially in includes/ or functions/ folders within the theme) for include(), require(), include_once(), or require_once() statements that use variables or user-controlled input in the file path without proper sanitization. Look for patterns like 'include($var)', 'require($_GET[...])', or similar.
    Affected if Dynamic file inclusion is found using unsanitized variables in include/require statements
  4. Verify the attack surface is exposed
    Check if the theme's PHP files that contain vulnerable include/require statements are accessible via web requests. Test by attempting a simple directory traversal in any theme-related URL parameters (e.g., ?template=../../../etc/passwd).
    Affected if The vulnerable code is accessible via HTTP requests without authentication protection

The environment is affected if the ThemeGoods Photography theme version is below 7.7.5 and the vulnerable dynamic file inclusion code is present and web-accessible.

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 ThemeGoods Photography theme to version 7.7.5 or later. If immediate update is not possible, implement input validation and web application firewall rules to block directory traversal patterns in request parameters.

Recommended fix Moderate confidence

ThemeGoods Photography version 7.7.5

  1. Update the ThemeGoods Photography WordPress theme to version 7.7.5 or later to remediate the Local File Inclusion vulnerability.
  2. Before updating, ensure you have a complete backup of your WordPress site including database and files.
  3. After updating, verify the theme version is correctly showing 7.7.5 or higher in the WordPress admin panel.
  4. Review theme functionality after the update to ensure all features are working correctly.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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