AgricolaWordPress extension · Axiomthemes
CVE-2025-58943
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 Agricola agricola allows PHP Local File Inclusion.This issue affects Agricola: from n/a through <= 1.1.0.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Agricola theme by axiomthemes. The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate input parameters to include arbitrary local PHP files. This can lead to sensitive file disclosure or remote code execution if attacker-controlled files exist on the server.
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
AgricolaWordPress extension
<= 1.1.0CVSS 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.
-
Identify if Agricola theme is installedLocate theme files - look for a folder named 'agricola' or 'agricola-theme' within your web application's wp-content/themes/ directory (if WordPress) or themes/ directory. Also check composer.json or package.json for axiomthemes/agricola dependencies.Affected if The Agricola theme by axiomthemes is found in the web application's theme directory.
-
Determine installed theme versionCheck the style.css file within the Agricola theme folder for the 'Version:' header, or check theme.json, composer.json, or any version file bundled with the theme.Affected if The installed version is 1.1.0 or lower, or the version cannot be determined (indicating an unpatched installation).
-
Locate file inclusion code patternsSearch the theme source code for dynamic include/require statements that use variables or request parameters - look for patterns like 'include($_GET[...])', 'require($param)', 'include($filename)', or similar where user input flows into include/require without sanitization.Affected if Code contains include/require statements using unsanitized variables or request parameters that could be manipulated.
-
Identify vulnerable input parametersExamine the identified file inclusion code to determine which GET/POST parameters accept file paths, then test whether those parameters can be manipulated to include arbitrary local files (e.g., ../../../../etc/passwd or similar path traversal).Affected if The file inclusion mechanism accepts path traversal sequences or allows arbitrary file paths from user input.
-
Check for signs of exploitationReview web server access logs for suspicious requests targeting the theme with path traversal patterns in parameters used by include/require statements. Also check for newly created or modified PHP files in writable directories.Affected if Access logs show exploitation attempts with path traversal patterns, or unknown malicious PHP files exist on the server.
You are affected if the Agricola theme version is 1.1.0 or lower AND the theme contains dynamic file inclusion code that uses unsanitized user input, allowing path traversal 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 dataUpgrade to a patched version of the Agricola theme. If no patch is available, implement strict input validation on all file inclusion parameters to restrict included files to an allowed whitelist, and ensure user input is never directly used in include/require statements.
Fix this in Agricola
Scoped from the published advisory
- 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-58943 — 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-58943 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