# CVE-2025-5497: slackero phpwcms Feedimport processing.inc.php deserialization

> Remote attackers can exploit unsafe deserialization in the Feedimport module to execute arbitrary code, requiring an upgrade to patched versions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2025
- **Updated:** 20 Aug 2025
- **Also known as:** GHSA-h582-52vg-77xv

## What is CVE-2025-5497?

CVE-2025-5497 is a medium-severity unsafe deserialization vulnerability in slackero phpwcms, published on 3 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in slackero phpwcms up to 1.9.45/1.10.8. The impacted element is an unknown function of the file include/inc_module/mod_feedimport/inc/processing.inc.php of the component Feedimport Module. Performing manipulation of the argument cnt_text results in deserialization. The attack can be initiated remotely. The exploit is now public and may be used. Upgrading to version 1.9.46 and 1.10.9 is sufficient to resolve this issue. The patch is named 41a72eca0baa9d9d0214fec97db2400bc082d2a9. It is recommended to upgrade the affected component.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Phpwcms Phpwcms.

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

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

## Is CVE-2025-5497 being exploited?

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

## Other vulnerabilities in slackero phpwcms

- [CVE-2021-36424](https://insights.sbomify.com/CVE-2021-36424/): Code injection in n/a (critical 9.8)
- [CVE-2020-21784](https://insights.sbomify.com/CVE-2020-21784/): Code injection in n/a (critical 9.8)
- [CVE-2021-36426](https://insights.sbomify.com/CVE-2021-36426/): File upload in n/a (high 8.8)
- [CVE-2006-7019](https://insights.sbomify.com/CVE-2006-7019/): Code injection in n/a (high 7.5)
- [CVE-2025-5499](https://insights.sbomify.com/CVE-2025-5499/): slackero phpwcms image_resized.php getimagesize deserialization (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5497 is a medium-severity unsafe deserialization vulnerability in slackero phpwcms, published on 3 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5497 exists.

Affected product: slackero phpwcms. 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-5497/ (Markdown: https://insights.sbomify.com/CVE-2025-5497/index.md)
```

## Sources

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

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