# CVE-2026-19658: Deserialization in Give Tributes

> Unauthenticated attackers can inject PHP objects via deserialization if specific form options are enabled, potentially leading to code execution or data exposure.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-wq6q-gx9m-7669

## What is CVE-2026-19658?

CVE-2026-19658 is a critical unsafe deserialization vulnerability in LiquidWeb Give Tributes, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Give Tributes plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.3.1 via deserialization of untrusted input . This makes it possible for unauthenticated attackers 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. This vulnerability is only reachable when the "Allow Multiple Recipients" option is enabled for the donation form, as the single-recipient code path applies sanitize_textarea_field() which would neutralize the payload. Exploitation additionally requires the eCard "Custom Message" option to be disabled, which is the plugin default: when it is enabled the personalized message becomes a required field and GiveWP's give_clean() blanks serialized input during validation, causing the donation to be rejected before it is stored.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-19658 being exploited?

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

Public exploit code:

- WordPress Give Tributes CVE-2026-19658: Python 3 checker, FOFA helper, legacy Give form exploit path (CWE-502, CVSS 9.8). (github_poc): https://github.com/murrez/CVE-2026-19658

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19658 is a critical unsafe deserialization vulnerability in LiquidWeb Give Tributes, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19658 in the wild and no public exploit code.

Affected product: LiquidWeb Give Tributes. 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-19658/ (Markdown: https://insights.sbomify.com/CVE-2026-19658/index.md)
```

## Sources

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

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