CVE-2024-31231
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Sizam Design Rehub allows PHP Local File Inclusion.This issue affects Rehub: from n/a through 19.6.1.
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 Rehub WordPress theme (versions up to 19.6.1) contains a path traversal vulnerability allowing attackers to perform Local File Inclusion (LFI) attacks. By manipulating path parameters, an attacker can include arbitrary PHP files from the server, potentially leading to remote code execution or sensitive file disclosure.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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.
-
Confirm Rehub theme installation and versionCheck the theme's style.css file in wp-content/themes/rehub/ for the 'Version:' header, or view the theme in WordPress Admin under Appearance > ThemesAffected if The installed version is 19.6.1 or any earlier version (versions up to 19.6.1 are affected)
-
Locate path-handling code in theme filesSearch theme PHP files for include, require, or similar functions that accept variable path inputs, such as: grep -r 'include\|require' --include='*.php' wp-content/themes/rehub/ | grep -i '\$' pay attention to files that handle template redirects or file loading based on request parametersAffected if The theme contains PHP files with include/require statements that use unsanitized path parameters from user input
-
Identify the vulnerable parameterExamine the code found in the previous step to identify which $_GET or $_POST parameter controls the path being included. Common parameter names include 'path', 'file', 'template', 'page', or similarAffected if A path-related parameter (e.g., 'path', 'file', 'template') is used in include/require statements without validation using functions like basename() or allowlist checking
-
Test for path traversal capabilityIf you have access to test the affected endpoint, observe whether the parameter accepts directory traversal sequences like '../' - check if the code performs any sanitization such as removing '..' or validating against an allowlistAffected if The path parameter allows '../' sequences and the included file path is not restricted to a whitelisted directory, enabling arbitrary file inclusion from the server filesystem
A user is affected if the Rehub theme version is 19.6.1 or earlier AND the theme contains code that uses path parameters from user input in include/require statements without proper validation or directory restriction.
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 canonicalization of file paths before inclusion. Use basename() to extract only the filename component, validate against an allowlist, and ensure all include/require statements use whitelisted directory paths.
- 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-2024-31231 — 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-2024-31231 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