# CVE-2025-0769: PixelYourSite 10.1.1.1 - Insecure deserialization

> An attacker can execute arbitrary code by exploiting insecure deserialization in the PixelYourSite WordPress plugin.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2025
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-3vg9-m54g-4c68

## What is CVE-2025-0769?

CVE-2025-0769 is a medium-severity unsafe deserialization vulnerability, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PixelYourSite - Your smart PIXEL (TAG) and API Manager 10.1.1.1 was found to be vulnerable. Unvalidated user input is used directly in an unserialize function in myapp/modules/facebook/facebook-server-a sync-task.php.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2025-0769 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0769 is a medium-severity unsafe deserialization vulnerability, published on 28 Feb 2025. 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-0769 in the wild and no public exploit code.

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-0769/ (Markdown: https://insights.sbomify.com/CVE-2025-0769/index.md)
```

## Sources

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

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