Is CVE-2026-122675 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-122675 being exploited in the wild.

How severe is CVE-2026-122675?

Medium severity, with a CVSS score of 5.4, published 7 November 2026.

Is there a fix for CVE-2026-122675?

Yes: fixed in 3.2.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-122675 attacked?

It is attacked over the network.

Am I affected by CVE-2026-122675?

Check whether you run Wpmet Wp Social at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-122675: Wpmet Wp Social cross-site request forgery

CVE-2026-122675 · Severity: medium · CVSS 5.4 · Published 2026-11-07

Wp Social is a WordPress plugin for social sharing and interaction features on websites. A cross-site request forgery (CSRF) vulnerability allows attackers to trick authenticated users into performing unintended actions, such as changing settings or making unwanted changes to their site. An attacker could craft a malicious link or page that, when visited by a logged-in administrator, performs actions without their knowledge or consent.

Vendors: Wpmet.

Quick answers

Is CVE-2026-122675 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-122675 being exploited in the wild.
How severe is CVE-2026-122675?: Medium severity, with a CVSS score of 5.4, published 7 November 2026.
Which products and versions are affected?: Wpmet Wp Social through 3.2.3.
Is there a fix for CVE-2026-122675?: Yes: fixed in 3.2.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-122675 attacked?: It is attacked over the network.
Am I affected by CVE-2026-122675?: Check whether you run Wpmet Wp Social at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.2.4

Technical details

The plugin fails to properly validate request origins, allowing CSRF attacks against authenticated users. The vulnerability requires user interaction (clicking a malicious link or visiting a crafted page) but does not require the attacker to be authenticated. A successful exploit could enable unauthorized configuration changes or other admin-level actions on affected WordPress sites.

Affected products

Wpmet Wp Social through 3.2.3

Timeline

2026-11-07: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.