Skip to main content
CVE-2026-122675VulnerabilityPublished

Wpmet Wp Social wp-social · Cross-Site Request Forgery (CSRF) Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-122675· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium : upgrade to 3.2.4 when convenient.

Data as of 7 Nov 2026, 10:04 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Patchstack)CVSS 3.15.4
Patch
Available – fixed in 3.2.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Wp Social to 3.2.4.

Affected software

ProductAffectedFixed in
Wp Socialwp-socialAffected
  • <3.2.4
Fixed in
  • 3.2.4

AI-suggested

If you cannot patch yet, consider implementing CSRF protections such as verifying CSRF tokens or restricting sensitive actions to trusted users.

Description

A Cross-Site Request Forgery (CSRF) vulnerability exists in the Wpmet Wp Social plugin (wp-social) affecting versions up to 3.2.3. This vulnerability allows an attacker to trick an authenticated user into submitting unwanted requests, potentially leading to unauthorized actions with limited impact on confidentiality and integrity but no impact on availability.

References

Community reviews

Loading reviews…