CVE-2025-52745
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 AncoraThemes Farm Agrico farmagrico allows PHP Local File Inclusion.This issue affects Farm Agrico: from n/a through <= 1.3.11.
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 confidenceLocal File Inclusion vulnerability in Farm Agrico theme where improper control of filename parameters in PHP include/require statements allows attackers to access arbitrary local files by manipulating the file path, potentially exposing sensitive system files or source code.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Farm Agrico theme versionLocate the theme's style.css file in wp-content/themes/farm-agrico/ and read the 'Version:' header, or check the theme dashboard if availableAffected if The installed version is unknown or within an unpatched version range
-
Find PHP files using include/requireSearch the theme directory for PHP files containing 'include' or 'require' statements, especially those referencing $_GET, $_POST, or $_REQUEST parameters in the file pathAffected if User-supplied input is directly used in include/require without sanitization
-
Inspect file inclusion parametersReview code for patterns like include($_GET['file']) or require($requested_file) where the parameter is not validated with basename() or an allowlistAffected if File path parameters accept relative paths like ../../../etc/passwd or ../wp-config.php
-
Check for exposed file read functionalityTest any theme parameters that might accept file paths (e.g., ?file=, ?page=, ?template=) by attempting to include a known safe file and observing the responseAffected if The application returns contents of arbitrary files when path traversal sequences are used
-
Verify input sanitizationSearch the theme code for sanitization functions like basename(), realpath(), or allowlist validation before using any user input in file inclusion operationsAffected if No sanitization function is found between user input and the include/require statement
A user is affected if the Farm Agrico theme is installed and contains PHP code that uses user-supplied parameters directly in include/require statements without proper validation using basename() or allowlist controls.
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 dataImplement strict input validation using allowlists or basename() functions to sanitize file inclusion parameters, and avoid using user-supplied input directly in include/require statements.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52745 — 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-52745 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