# CVE-2025-7640: hiWeb Export Posts <= 0.9.0.0 - Cross-Site Request Forgery to Arbitrary File Deletion

> Attackers can trick admins into deleting arbitrary files, potentially causing remote code execution, via CSRF in the hiWeb Export Posts plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-xrp5-4mrh-cc5r

## What is CVE-2025-7640?

CVE-2025-7640 is a high-severity vulnerability in den-media hiWeb Export Posts, published on 24 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The hiWeb Export Posts plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.9.0.0. This is due to missing or incorrect nonce validation on the tool-dashboard-history.php file. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php), via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

## Which versions are affected by CVE-2025-7640?


## How do I fix CVE-2025-7640?

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

## Is CVE-2025-7640 being exploited?

There is no known exploitation of CVE-2025-7640 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7640 and fix it if it is affected.

What it is: CVE-2025-7640 is a high-severity vulnerability in den-media hiWeb Export Posts, published on 24 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7640 in the wild and no public exploit code.

Affected product: den-media hiWeb Export Posts. 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-2025-7640/ (Markdown: https://insights.sbomify.com/CVE-2025-7640/index.md)
```

## Sources

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

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