dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-30841

CRITICAL · 9.9 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in adamskaat Countdown & Clock countdown-builder allows Remote Code Inclusion.This issue affects Countdown & Clock: from n/a through <= 2.8.8.

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 confidence

A path traversal vulnerability in the adamskaat Countdown & Clock WordPress plugin (versions up to 2.8.8) allows remote code inclusion via improper limitation of file pathnames, enabling attackers to access restricted directories and execute arbitrary code on the server.

MitigationUpgrade to the latest version of Countdown & Clock plugin when available, or disable the plugin until patched. Implement web application firewall rules to block directory traversal patterns in HTTP requests.

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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Countdown & Clock plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a folder containing 'countdown' or 'clock' in the name
    Affected if The adamskaat Countdown & Clock plugin is present on the WordPress site
  2. Check installed plugin version
    Open the plugin's main PHP file or readme.txt in wp-content/plugins/[plugin-folder] and locate the Version header, or view the plugin details in WordPress admin plugins list
    Affected if The version is 2.8.8 or lower (any version up to and including 2.8.8)
  3. Identify plugin AJAX or file-inclusion endpoints
    Review plugin source files for functions that accept file path parameters (such as include, require, file_get_contents, readfile) and check for admin-ajax.php or custom AJAX handlers registered via wp_ajax_ hooks
    Affected if The plugin contains file-inclusion functions that process user-supplied path parameters without validation
  4. Inspect web server access logs for path traversal patterns
    Search HTTP access logs for requests containing traversal sequences such as ../, ..\, or absolute path attempts targeting sensitive directories like /etc/ or /windows/
    Affected if Log entries show directory traversal attempts (../../, /etc/passwd, etc.) targeting the plugin's file-handling functionality
  5. Check for unauthorized file creation or modification
    Review files in wp-content and child directories for unexpected new PHP files or modifications to existing plugin files, particularly those created or modified after the vulnerability disclosure date
    Affected if Unknown PHP files exist in wp-content or plugin directories, or existing plugin files have been modified without your knowledge

If the Countdown & Clock plugin is installed and the version is 2.8.8 or lower, the environment is affected by this path traversal vulnerability and may allow remote code execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of Countdown & Clock plugin when available, or disable the plugin until patched. Implement web application firewall rules to block directory traversal patterns in HTTP requests.

Recommended fix Moderate confidence

Update to the latest available version of the Countdown & Clock plugin (version newer than 2.8.8)

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the 'Countdown & Clock' plugin by adamskaat.
  4. 4. Check if an update is available - if so, update to the latest version.
  5. 5. If no update is visible in WordPress, manually download the latest version from the WordPress plugin repository and reinstall.
  6. 6. Verify the plugin is updated to a version newer than 2.8.8.
  7. 7. Test that the countdown builder functionality works correctly after the update.
  8. 8. Monitor the site for any unusual activity following the update.
Caveat Standard minor version upgrades typically have low risk, but test in staging first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30841 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30841 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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