GiardinoWordPress extension · Axiomthemes
CVE-2025-60067
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 axiomthemes Giardino giardino allows PHP Local File Inclusion.This issue affects Giardino: from n/a through <= 1.1.10.
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 confidenceThe Giardino theme by axiomthemes contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements without adequate sanitization. This allows attackers to include arbitrary local PHP files, potentially leading to code execution or sensitive data disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GiardinoWordPress extension
<= 1.1.10CVSS 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.
-
Confirm Giardino theme installationLocate the Giardino theme directory in the web application's theme folder (typically /wp-content/themes/giardino/ or similar). Verify the theme files exist on the system.Affected if The Giardino theme directory is present on the server.
-
Identify installed theme versionOpen the theme's style.css or theme.json file within the Giardino theme directory and locate the Version field in the header comment or version entry.Affected if The reported version is 1.1.10 or lower.
-
Locate dynamic include/require statementsSearch all PHP files in the Giardino theme directory for include, require, include_once, or require_once statements that incorporate variables (such as $_GET, $_POST, or $_REQUEST) directly into the file path without sanitization.Affected if PHP files contain include/require statements using unsanitized user input for file paths.
-
Inspect URL parameters used in includesReview any identified vulnerable include/require patterns and determine which URL parameters (GET/POST) control the included file path. Test if these parameters can be manipulated to include arbitrary local files.Affected if URL parameters can be manipulated to include files outside the intended theme directory.
-
Check for sensitive file accessIf vulnerable include patterns exist, attempt to include known local PHP files (such as wp-config.php or other configuration files) using the vulnerable parameter to confirm the LFI capability.Affected if Arbitrary local PHP files can be included and executed through the vulnerable parameter.
You are affected if the Giardino theme version is 1.1.10 or lower AND the theme contains include/require statements that use unsanitized user-supplied input to determine which files to load.
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 Giardino to the latest version, or apply input validation/sanitization to all include/require statements to ensure only whitelisted files can be included.
Fix this in Giardino
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60067 — 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-60067 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