# CVE-2025-67617: WordPress Consult Aid theme <= 1.4.3 - PHP Object Injection vulnerability

> An attacker can exploit PHP object injection in the Consult Aid theme to potentially execute arbitrary code on the WordPress site.

- **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 Jan 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-94gj-3qj6-w8qv

## What is CVE-2025-67617?

CVE-2025-67617 is a critical unsafe deserialization vulnerability in themeton Consult Aid, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Deserialization of Untrusted Data vulnerability in themeton Consult Aid consultaid allows Object Injection.This issue affects Consult Aid: from n/a through <= 1.4.3.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2025-67617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67617 is a critical unsafe deserialization vulnerability in themeton Consult Aid, published on 22 Jan 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-2025-67617 in the wild and no public exploit code.

Affected product: themeton Consult Aid. 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-67617/ (Markdown: https://insights.sbomify.com/CVE-2025-67617/index.md)
```

## Sources

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

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