Catch Dark ModeWordPress extension · Catchthemes
CVE-2025-32154
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 Catch Themes Catch Dark Mode catch-dark-mode allows PHP Local File Inclusion.This issue affects Catch Dark Mode: from n/a through <= 2.0.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 · moderate confidenceA Local File Inclusion (LFI) vulnerability in the Catch Dark Mode WordPress plugin allows attackers to include arbitrary PHP files from the server due to improper control of filename parameters in include/require statements. This can lead to remote code execution if attackers can include maliciously placed PHP 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
Catch Dark ModeWordPress extension
< 2.1CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check the installed version of Catch Dark Mode pluginNavigate to WordPress Admin > Plugins > Installed Plugins > Catch Dark Mode. The version number is displayed below the plugin name. Alternatively, check the main plugin file (usually catch-dark-mode.php) for the 'Version' header in the plugin comment block.Affected if The displayed version is less than 2.1 (e.g., 2.0, 1.9, etc.)
-
Verify the plugin is currently activeIn WordPress Admin > Plugins, check if Catch Dark Mode shows as 'Active' under the plugin status.Affected if The plugin is active and the version is below 2.1
-
Identify vulnerable include/require patterns in plugin filesUsing a file manager or grep search, examine PHP files in the plugin directory (wp-content/plugins/catch-dark-mode/) for include, include_once, require, or require_once statements that use variables without sanitization, such as include($file), include($_GET['file']), or similar dynamic file inclusion.Affected if Any include/require statements directly use unsanitized user input (like $_GET, $_POST, or未经滤的变量) and the plugin version is below 2.1
-
Check for publicly accessible file inclusion triggersReview the plugin's AJAX handlers or public-facing PHP files to see if they accept file path parameters that could be manipulated for directory traversal (e.g., ?file=../../../../etc/passwd).Affected if The plugin accepts file path parameters in HTTP requests without proper validation and the version is below 2.1
You are affected if the Catch Dark Mode plugin version is below 2.1 AND the plugin is active on your WordPress site, as the LFI vulnerability exists in this version range.
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.
dbcve · scoped2.1
Update Catch Dark Mode to the latest version immediately. If no update is available, disable the plugin. Additionally, ensure PHP configuration disable allow_url_fopen and allow_url_include, and implement Web Application Firewall rules to detect directory traversal patterns.
Catch Dark Mode 2.1
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Dashboard > Updates or Appearance > Themes
- 3. Check for available updates to the Catch Dark Mode theme
- 4. If an update to version 2.1 or later is available, click Update Now
- 5. Alternatively, download Catch Dark Mode version 2.1 from the official WordPress theme repository
- 6. Upload and install the updated theme via Appearance > Themes > Add New > Upload Theme
- 7. Verify the theme is running version 2.1 or later after update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Catch Dark Mode
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32154 — 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-32154 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