# CVE-2025-1913: Product Import Export for WooCommerce <= 2.5.0 - Authenticated (Admin+) PHP Object Injection via form_data Parameter

> Authenticated administrators can exploit PHP object injection via the form_data parameter, potentially leading to code execution or data exposure if a POP chain exists.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8h4g-52x5-5r4v

## What is CVE-2025-1913?

CVE-2025-1913 is a high-severity unsafe deserialization vulnerability in webtoffee Product Import Export for WooCommerce – Import Export Product CSV Suite, published on 26 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Product Import Export for WooCommerce – Import Export Product CSV Suite plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.5.0 via deserialization of untrusted input from the 'form_data' parameter This makes it possible for authenticated attackers, with Administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Webtoffee Product Import Export for Woocommerce.

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

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

## Is CVE-2025-1913 being exploited?

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

Public exploit code:

- A PoC demonstrating CVE-2025-1913, showing how the plugin’s unsafe unserialize handling can lead to high-impact behavior in controlled environments. Contains a harmful payload for authorized testing only. Use strictly in isolated labs and for defensive research. (github_poc): https://github.com/S0haib518-KSA/CVE-2025-1913-PoC

## Other vulnerabilities in webtoffee Product Import Export for WooCommerce – Import Export Product CSV Suite

- [CVE-2024-30231](https://insights.sbomify.com/CVE-2024-30231/): WordPress Product Import Export for WooCommerce plugin <= 2.4.1 - Arbitrary File Upload vulnerability (critical 9.1)
- [CVE-2024-22152](https://insights.sbomify.com/CVE-2024-22152/): WordPress Product Import Export for WooCommerce Plugin <= 2.3.7 is vulnerable to Arbitrary File Upload (high 8.0)
- [CVE-2025-1912](https://insights.sbomify.com/CVE-2025-1912/): Server-side request forgery in Product Import Export for WooCommerce – Import Export Product CSV Suite (high 7.6)
- [CVE-2025-1769](https://insights.sbomify.com/CVE-2025-1769/): Path traversal in Product Import Export for WooCommerce – Import Export Product CSV Suite (medium 4.9)
- [CVE-2025-1911](https://insights.sbomify.com/CVE-2025-1911/): Path traversal in Product Import Export for WooCommerce – Import Export Product CSV Suite (low 2.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1913 is a high-severity unsafe deserialization vulnerability in webtoffee Product Import Export for WooCommerce – Import Export Product CSV Suite, published on 26 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1913 in the wild and no public exploit code.

Affected product: webtoffee Product Import Export for WooCommerce – Import Export Product CSV Suite. 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-1913/ (Markdown: https://insights.sbomify.com/CVE-2025-1913/index.md)
```

## Sources

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

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