CVE-2025-68064
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 · uneditedContributor Local File Inclusion in Goya Core < 1.0.9.4 versions.
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 confidenceA Local File Inclusion (LFI) vulnerability in Goya Core versions before 1.0.9.4 allows users with Contributor-level permissions to read arbitrary files on the server via unsanitized file path inputs in the plugin.
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.
-
Check if Goya Core plugin is installedNavigate to WordPress admin > Plugins and look for 'Goya Core' in the installed plugins list, or check the plugin files in wp-content/plugins/ for the goya-core directoryAffected if Goya Core plugin is not installed on the WordPress site
-
Determine installed Goya Core versionIn WordPress admin > Plugins, find Goya Core and view the version number displayed, or check the main plugin file header in wp-content/plugins/goya-core/ for the 'Version' tagAffected if Version is present and below 1.0.9.4 (for example, 1.0.9.3, 1.0.8.x, etc.)
-
Identify Contributor-level usersIn WordPress admin > Users, filter or scroll through the user list to identify accounts with the 'Contributor' roleAffected if At least one user account has Contributor role assigned
-
Verify file-related functionality is accessible to ContributorsLog in as a Contributor user and attempt to access any file upload, file selection, or file path input features within Goya Core (such as image/file uploaders, template file loaders, or custom file path fields)Affected if Contributor users can access and interact with file path input fields in the plugin
Environment is affected if Goya Core version is before 1.0.9.4 AND Contributor-level user accounts exist with access to file-related features in the plugin
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.
dbcve · scopedUpgrade Goya Core to version 1.0.9.4 or later. If immediate upgrade is not possible, restrict contributor-level users' access and monitor for suspicious file access patterns.
Goya Core 1.0.9.4 or later
- Backup your current Goya Core installation and database before upgrading
- Update Goya Core to version 1.0.9.4 or later
- After upgrading, verify the application functions correctly and the vulnerability is resolved by testing the affected component
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68064 — 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-68064 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