# CVE-2026-73033: Sucuri WordPress Plugin 2.7.3 Path Traversal via integrity.lib.php

> Authenticated administrators can delete arbitrary files via path traversal in the Sucuri WordPress plugin, potentially causing site outage.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-vxwv-hcj3-j79g

## What is CVE-2026-73033?

CVE-2026-73033 is a high-severity path traversal vulnerability in sucuri-wordpress-plugin, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Sucuri Security WordPress plugin through version 2.7.3 contains a path traversal vulnerability in the pageIntegritySubmission() method in src/integrity.lib.php that allows authenticated administrators to delete arbitrary files by supplying directory traversal sequences in the sucuriscan_integrity parameter. Attackers can manipulate the unsanitized file path concatenated with ABSPATH to traverse outside the WordPress installation directory and invoke unlink() on sensitive files such as wp-config.php and .htaccess, causing site outage or enabling malicious reinstallation.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-73033?


## How do I fix CVE-2026-73033?

No fix has been published for CVE-2026-73033 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73033 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73033 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73033 and fix it if it is affected.

What it is: CVE-2026-73033 is a high-severity path traversal vulnerability in sucuri-wordpress-plugin, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73033 exists.

Affected product: sucuri-wordpress-plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73033/ (Markdown: https://insights.sbomify.com/CVE-2026-73033/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73033
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73033
- OSV: https://osv.dev/vulnerability/CVE-2026-73033

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73033/
Summaries are generated and may contain mistakes; the official description above is the record.