# CVE-2023-49778: WordPress Sayfa Sayaç Plugin <= 2.6 is vulnerable to PHP Object Injection

> An attacker can exploit PHP object injection in the Sayfa Sayac WordPress plugin to potentially execute arbitrary code.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** 21 Dec 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-jfg8-q228-h5m4

## What is CVE-2023-49778?

CVE-2023-49778 is a critical unsafe deserialization vulnerability in Hakan Demiray Sayfa Sayac, published on 21 Dec 2023. 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 Hakan Demiray Sayfa Sayac.This issue affects Sayfa Sayac: from n/a through 2.6.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-49778?

It affects 1 product.


Products: Dmry Sayfa Sayac.

## How do I fix CVE-2023-49778?

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

## Is CVE-2023-49778 being exploited?

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

## Other vulnerabilities in Hakan Demiray Sayfa Sayac

- [CVE-2023-49776](https://insights.sbomify.com/CVE-2023-49776/): WordPress Sayfa Sayaç Plugin <= 2.6 is vulnerable to SQL Injection (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49778 and fix it if it is affected.

What it is: CVE-2023-49778 is a critical unsafe deserialization vulnerability in Hakan Demiray Sayfa Sayac, published on 21 Dec 2023. 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-2023-49778 in the wild and no public exploit code.

Affected product: Hakan Demiray Sayfa Sayac. 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-2023-49778/ (Markdown: https://insights.sbomify.com/CVE-2023-49778/index.md)
```

## Sources

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

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