Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/mor-golan/cve-2026-122675
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPenetration TestingRed Teaming
GitHubmor-golan/cve-2026-122675

CVE-2026-122675

Proof-of-concept for CVE-2026-122675, a CSRF in the Wp Social WordPress plugin (<=3.2.3) that lets an attacker overwrite OAuth provider credentials via a forged admin request.

View Repository
5 days agoNot yet reviewed
Website

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    593
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    371
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    336
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    326
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    322

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-122675: Cross Site Request Forgery (CSRF) in Wp Social WordPress Plugin

CVECVE-2026-122675
PluginWp Social (wp-social)
Affected<= 3.2.3
Fixed in3.2.4
SeverityCVSS 5.4 Medium
Attacker needsNo account. A logged in administrator has to open an attacker page
AdvisoryPatchstack
Writeupmor-golan.github.io/research/cve-2026-122675-wp-social

The Wp Social plugin by Wpmet saves its social login provider settings in Admin_Settings::content_xs_providers() (inc/admin-settings.php) on the presence of the xs_provider_submit_form POST key alone. There is no nonce check and no referer check on that path, while every sibling save branch in the same class verifies a nonce.

An attacker with no account hosts a page that posts to the providers screen. When a logged in administrator opens it, the browser sends the administrator's cookies and the plugin overwrites the xs_provider_data option, which holds the OAuth client ID and client secret for every social login provider the site uses. I tested on 3.2.1. The official affected range is every version up to and including 3.2.3.

Precondition: the plugin's one time onboarding wizard has been finished, which is the normal state of a site that uses the plugin.

Usage

Lab setup: WordPress at http://localhost:8080 with Wp Social 3.2.1 installed, the onboarding wizard finished, and an administrator account.

Check the starting values:

wp option get xs_provider_data --format=json

Browser delivery (the real attack)

Serve the attacker page from a different origin than the target. 127.0.0.1 and localhost are different sites to the browser, so this makes the delivery cross site:

python3 -m http.server 9098 --bind 127.0.0.1

Log in to http://localhost:8080/wp-admin/ as the administrator in a browser, then open in the same browser:

http://127.0.0.1:9098/csrf-poc.html?target=http://localhost:8080

The page submits itself. The administrator lands on the plugin's providers screen with "Providers data have been updated." Read the option again:

wp option get xs_provider_data --format=json
# {"facebook":{"id":"ATTACKER-CLIENT-ID","secret":"ATTACKER-CLIENT-SECRET","enable":"on"}}

curl version

Sends the same request without a browser, to show the handler accepts it with no nonce. It needs a cookie jar with an administrator session:

curl -s -c jar.txt -d 'log=ADMIN&pwd=PASSWORD&wp-submit=Log+In&testcookie=1' \
     http://localhost:8080/wp-login.php -o /dev/null
./csrf-poc.sh http://localhost:8080
# or: TARGET=http://localhost:8080 ./csrf-poc.sh
wp option get xs_provider_data --format=json

Files

  • csrf-poc.html: attacker page that posts the forged providers form as soon as it loads. Target from ?target=, default http://localhost:8080.
  • csrf-poc.sh: the same request with curl and an administrator cookie jar. Target from the first argument or TARGET, default http://localhost:8080.

Disclaimer

For authorized security testing and education only. Run it only against systems you own or are permitted to test.

Credit

Found and reported by Mor Golan, Israeli CVE hunter and bug bounty hunter.

  • mor-golan.github.io
  • Writeup
  • CVE-2026-122675
Download Tool