cve.bz

CVE-2026-122675 wpmet wp social: Cross Site Reference Forgery

5.4 mediumEPSS 0.09%Fix available

Medium (5.4) in wpmet wp social. EPSS 0.09% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS
0.09% estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-122675 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-122675?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-122675?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-122675 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-122675

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-122675](https://cve.bz/cve/badge/CVE-2026-122675.svg)](https://cve.bz/cve/CVE-2026-122675)

HTML:

<a href="https://cve.bz/cve/CVE-2026-122675"><img src="https://cve.bz/cve/badge/CVE-2026-122675.svg" alt="CVE-2026-122675"></a>

Affected

  • wpmet:wp social

Versions

From the CNA's record in the CVE List.

ProductAffected
Wpmet Wp Socialthrough 3.2.3

Fixed in

ProductFixed in
Wpmet Wp Social3.2.4

Fix and patched versions

  • Wpmet Wp Social: fixed in 3.2.4

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • Mor-Golan/CVE-2026-122675 0 stars, Shell, created
    CVE-2026-122675: Cross Site Request Forgery (CSRF) in Wp Social WordPress Plugin. PoC by Mor Golan.

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON