PantryWordPress extension · Axiomthemes
CVE-2025-58929
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 Pantry pantry allows PHP Local File Inclusion.This issue affects Pantry: from n/a through <= 1.4.
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 axiomthemes Pantry theme contains a PHP Local File Inclusion (LFI) vulnerability where user-controlled input is used in include/require statements without proper validation. An attacker could manipulate file path parameters to include arbitrary local files, potentially leading to code execution if they can upload files or access sensitive configuration files.
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
PantryWordPress extension
<= 1.4CVSS 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 the installed Pantry theme versionLocate the theme's style.css file in wp-content/themes/pantry/ and read the version declared in the theme header comment. Alternatively, check the version in the theme's functions.php file if defined there.Affected if The version listed is 1.4 or lower.
-
Confirm the theme is activeCheck if the Pantry theme is currently enabled in your WordPress installation by examining wp_options table for 'template' or 'stylesheet' values, or via WordPress admin dashboard under Appearance > Themes.Affected if The Pantry theme is the currently active theme.
-
Locate include and require statements in theme filesSearch all PHP files in the Pantry theme directory (wp-content/themes/pantry/) for include, require, include_once, or require_once functions. Examine each to see if they use variables from $_GET, $_POST, or $_REQUEST without sanitization.Affected if Any include/require statement uses raw user input (such as $_GET['file'], $_REQUEST['page'], etc.) without validation.
-
Inspect URL parameters used for file loadingTest common parameter names like 'file', 'page', 'template', 'include', 'path', or 'load' by requesting pages with these parameters (e.g., ?file=config.php) and observe if the server attempts to include arbitrary files.Affected if The application returns file contents or includes files based on user-supplied parameters without validation.
You are affected if the Pantry theme version is 1.4 or lower and your server processes file inclusion parameters without proper validation.
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 and sanitization on all parameters used in include/require statements, use allowlists for permitted file paths, and avoid using user input directly in file inclusion functions.
Fix this in Pantry
Scoped from the published advisory
- Consultation4.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58929 — 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-58929 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