The GigWordPress extension · Axiomthemes
CVE-2025-58934
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 The Gig thegig allows PHP Local File Inclusion.This issue affects The Gig: from n/a through <= 1.18.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 · high confidenceThe Gig WordPress theme by axiomthemes contains a PHP Local File Inclusion (LFI) vulnerability caused by improper control of filename parameters in include/require statements. This allows authenticated attackers to read sensitive files on the server via path traversal attacks.
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
The GigWordPress extension
<= 1.18.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.
-
Verify The Gig theme is installedCheck your WordPress installation under wp-content/themes/ for a folder named 'the-gig' or 'thegig', or view installed themes via WordPress admin under Appearance > ThemesAffected if The theme folder exists in the WordPress themes directory
-
Determine installed theme versionOpen the style.css file in the theme folder and look for the 'Version:' comment in the file header, or check the theme version displayed in WordPress admin under Appearance > ThemesAffected if Version is 1.18.0 or lower (any version up to and including 1.18.0)
-
Confirm user authentication is possibleCheck if any user accounts exist in the WordPress database (wp_users table) or via WordPress admin under Users > All UsersAffected if At least one user account exists with any role (subscriber, contributor, author, editor, or administrator)
-
Locate potentially vulnerable include/require patternsSearch PHP files in the theme folder for include, require, include_once, or require_once statements that use variable parameters, such as: include($file); require($path); include($_GET['...']);Affected if Theme contains include/require statements using unsanitized variables that could accept path traversal sequences like ../
-
Review access logs for exploitation attemptsExamine web server access logs (Apache error.log, Nginx access.log) or WordPress debug logs for suspicious requests containing ../, ..\, or null byte (%00) in parameters passed to theme PHP filesAffected if Log entries show path traversal patterns being passed to theme scripts
Your environment is affected if The Gig theme version is 1.18.0 or lower AND the theme is actively installed on a WordPress site with at least one user account.
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 dataUpdate The Gig theme to the latest patched version. If no patch is available, audit and harden file inclusion logic to enforce strict whitelist-based validation and disable allow_url_include in PHP configuration.
Fix this in The Gig
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58934 — 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-58934 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