# CVE-2024-6709: Sync Post With Other Site <= 1.6 - Missing Authorization to Authenticated (Subscriber+) Post Creation and Update

> Authenticated subscribers can create or update posts due to missing capability checks in the Sync Post With Other Site plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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 Aug 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7698-w222-8jf9

## What is CVE-2024-6709?

CVE-2024-6709 is a medium-severity missing authorization vulnerability in kp4coder Sync Post With Other Site, published on 3 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Sync Post With Other Site plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'sps_add_update_post' function in all versions up to, and including, 1.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create new draft posts and update existing posts.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-6709?

It affects 1 product.


Products: Syncpostwithothersite Sync Post With Other Site.

## How do I fix CVE-2024-6709?

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

## Is CVE-2024-6709 being exploited?

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

## Other vulnerabilities in kp4coder Sync Post With Other Site

- [CVE-2024-32082](https://insights.sbomify.com/CVE-2024-32082/): WordPress Sync Post With Other Site plugin <= 1.9.1 - Cross Site Request Forgery (CSRF) to XSS vulnerability (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6709 and fix it if it is affected.

What it is: CVE-2024-6709 is a medium-severity missing authorization vulnerability in kp4coder Sync Post With Other Site, published on 3 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6709 in the wild and no public exploit code.

Affected product: kp4coder Sync Post With Other Site. 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-2024-6709/ (Markdown: https://insights.sbomify.com/CVE-2024-6709/index.md)
```

## Sources

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

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