CVE-2025-68530
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 pavothemes Bookory bookory allows PHP Local File Inclusion.This issue affects Bookory: from n/a through <= 2.2.7.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the Bookory WordPress theme by pavothemes. The theme improperly controls filenames in PHP include/require statements, allowing attackers to manipulate path parameters to include arbitrary local PHP files. This can lead to remote code execution if attacker-controlled files can be uploaded or accessed on the server.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Bookory theme installationLocate the Bookory theme directory in the WordPress installation (typically wp-content/themes/bookory) and identify the theme version from style.css or theme.json in the theme root folderAffected if Bookory theme is present in the WordPress themes directory with an unpatched version
-
Review file inclusion functionsSearch theme PHP files for include, require, include_once, or require_once statements that use variable or request-based parameters (e.g., include($_GET['file']) or include($some_var))Affected if The theme contains dynamic file inclusion calls using unsanitized input from $_GET, $_POST, or other user-controllable sources
-
Identify vulnerable parameter handlingExamine PHP files that handle page/template routing or file path parameters (common in template-loader.php, header.php, or custom template files). Look for code that directly passes request parameters to include/require statements without validationAffected if Path parameters from HTTP requests are used in include/require statements without strict whitelist validation or basename() sanitization
-
Check uploaded files accessible to PHPInspect the wp-content/uploads directory and any custom upload directories for .php files that the web server can executeAffected if Executable PHP files exist in web-accessible directories that could be included via the LFI vulnerability to achieve code execution
-
Verify PHP configurationCheck php.ini for allow_url_include setting (should be Off) and review if open_basedir restrictions are in place to limit accessible directoriesAffected if allow_url_include is enabled or no open_basedir restrictions exist, increasing exploitability of the LFI
The environment is affected if the Bookory theme is installed with vulnerable file inclusion code that uses unsanitized request parameters, allowing attackers to manipulate path arguments to include arbitrary local files.
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 dataUpdate Bookory theme to the latest patched version. If no patch is available, implement strict whitelist-based validation on all file inclusion parameters and disable allow_url_include in PHP configuration.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68530 — 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-68530 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