dbcve.org
Wp SquaredWordPress extension · Cpanel

CVE-2026-29205

HIGH · 8.6 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 124.0.38 / 126.0.59 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Incorrect privileges management and insufficient path filtering allow to read arbitrary file on the server via the cpdavd attachment download endpoints.

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 and privilege escalation vulnerability in cpdavd's attachment download endpoints allows unauthenticated or improperly authenticated users to read arbitrary files on the server due to insufficient path validation and incorrect privilege enforcement.

MitigationImplement strict path canonicalization with allowlist validation, enforce proper authentication and authorization checks on all file access operations, and restrict the web service process to minimum necessary file system permissions.

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
Wp SquaredWordPress extension
Affected:>= 120.1.0, < 136.1.12
CpanelApplication
Affected:>= 120.0.0, < 124.0.38>= 126.0.0, < 126.0.59>= 130.0.0, < 130.0.23>= 130.0.23, < 130.0.23>= 132.0.0, < 132.0.32>= 134.0.0, < 134.0.26>= 136.0.0, < 136.0.10
WhmApplication
Affected:>= 120.0.0, < 124.0.38>= 126.0.0, < 126.0.59>= 130.0.0, < 130.0.23>= 132.0.0, < 132.0.32>= 134.0.0, < 134.0.26>= 136.0.0, < 136.0.10

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

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. Identify if cpdavd service is running
    Run 'ps aux | grep cpdavd' or check systemd service status with 'systemctl status cpdavd'
    Affected if cpdavd process is running and exposed to network access
  2. Determine installed cpdavd version
    Check package version via 'rpm -q cpdavd' or 'dpkg -l cpdavd', or inspect '/usr/local/cpanel/version' for cPanel version which includes cpdavd
    Affected if installed version falls within any vulnerable version range (compare to CVE reference) or version cannot be determined
  3. Verify attachment download endpoints are accessible
    Test HTTP access to cpdavd paths such as /webmail/attachment or /cgi-sys/attachment endpoints, or review web server configuration for cpdavd alias directives
    Affected if cpdavd attachment download endpoints are exposed without authentication or with user-level authentication
  4. Check for path traversal protection in cpdavd configuration
    Inspect cpdavd configuration files in /var/cpanel/conf/cpdavd or /usr/local/cpanel/conf/ for path validation settings, and review Apache/Nginx vhost configs for cpdavd-related rewrite rules
    Affected if No whitelist-based path validation or traversal sequence filtering is configured for attachment handlers
  5. Test for path traversal vulnerability
    If endpoints are accessible, attempt a controlled test request with '../' sequences (e.g., /webmail/attachment/..%2F..%2F..%2Fetc%2Fpasswd) using curl or browser; otherwise review access logs for suspicious traversal patterns
    Affected if Server responds with file contents outside intended directory or returns unexpected file data in response

A user is affected if cpdavd is running with exposed attachment download endpoints AND lacks proper path validation AND the installed version matches vulnerable releases.

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.

From vendor data
Upgrade available Upgrade to 124.0.38 / 126.0.59 / 130.0.23 or later
Fixed in 124.0.38126.0.59130.0.23
Interim mitigation

Implement strict path canonicalization with allowlist validation, enforce proper authentication and authorization checks on all file access operations, and restrict the web service process to minimum necessary file system permissions.

Fix this in Wp Squared Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29205 — 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-2026-29205 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