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-86583 — Proof-of-concept exploit for CVE-2026-86583, a CSV import escape-character mismatch in the WordPress import-users-from-csv-with-meta plugin that lets a subscriber escalate to administrator. | Kitploit
Tools/GitHubGitHub/saretawa/cve-2026-86583
Privilege EscalationVulnerability AnalysisExploitationWeb Application ExploitationPenetration Testing
GitHubsaretawa/cve-2026-86583

CVE-2026-86583

Proof-of-concept exploit for CVE-2026-86583, a CSV import escape-character mismatch in the WordPress import-users-from-csv-with-meta plugin that lets a subscriber escalate to administrator.

View Repository
15 days agoNot yet reviewed
Share

This exploit works only when you have subscriber user credentials on WordPress and trigger is not dependent on user, you need to either wait for administrator to do it or manually login as administrator and trigger it. scope can also change and it's much easier if scope change is the goal, because while it can be reimported into same WordPress instance, it can also be imported into other WordPress deployment resulting in compromise of other machines while vulnerable plugin is present. in case of scope change Update existing users and Update roles for existing users? will no longer be required unless user is already present on the instance.

two lines are patched in classes/import.php:

vulnerable (≤ 2.4.17):

$header_data = $header_manager->fgetcsv( $delimiter );
...
while( $data = $manager->fgetcsv( $delimiter ) ):

patched (2.4.18):

$header_data = $header_manager->fgetcsv( $delimiter, '"', "\0" );
...
while( $data = $manager->fgetcsv( $delimiter, '"', "\0" ) ):

so in the vulnerable version fgetcsv is called with only the delimiter

fgetcsv is a PHP function that reads one line from an open file and splits it into an array of fields, understanding CSV rules (quotes, escapes). So instead of you parsing commas by hand, it hands back a ready-made array.

say a file users.csv contains:

Alice,subscriber,ally
"Bob, Jr.",editor,bobby

reading it line by line:

$f = new SplFileObject("users.csv");
while ($row = $f->fgetcsv(",", '"')) {
    print_r($row);
}

we will get something like this:

Array ( [0] => Alice      [1] => subscriber  [2] => ally )
Array ( [0] => Bob, Jr.   [1] => editor      [2] => bobby )

notice "Bob, Jr." has a comma inside it, but because it's wrapped in the " enclosure, fgetcsv knows that comma is data, not a separator so it stays as one field Bob, Jr. instead of splitting into Bob and Jr.. That enclosure logic is exactly the thing the bug abuses

$delimiter is just the separator character you tell fgetcsv to split on

only the first argument (the delimiter) separates cells. The other two do different jobs:

fgetcsv( $delimiter, $enclosure, $escape )

so youve got one separator and two "how to interpret quotes/specials" controls.

so when you call fgetcsv($delimiter) with only the delimiter, PHP fills in defaults for the missing two:

fgetcsv( $delimiter, '"', '\\' )

enclosure defaults to " (and that is fine), but the escape defaults to backslash \

now look at the exporter the code that writes the CSV:

fputcsv( $buffer, $row, $delimiter, '"', "\0" ) // <-- writes with NUL escape

writer says "NUL is my escape character." The reader says "backslash is my escape character." They disagree on what the escape character is and that causes the issues

the cell boundary shifts what the writer intended as two separate cells, the reader glues into one and everything after it slides over by one column.

normal exported row looks like in the CSV for those three columns:

"John Doe","subscriber","johndoe"

reader sees three clean cells: display_name = John Doe, role = subscriber, nickname = johndoe

so setting display_name to saretawa\ can be a potential way to escalate because we can modify nickname as a role administrator

but you would have to compensate for the field that is missing and for this to work then users need to be exported with plugin and reimported by administrator and when importing Update existing users needs to be checked and Update roles for existing users? also needs to be checked, idk if its possible to also add a user probably is and you wont need Update existing users but I am too lazy and busy to do that

so trigger was like this:

First Name: saretawa

Nickname: ,administrator,x

Display name: hack,y\ (type that in first name select from drop down then swap back)

or just run the exploit.py it will set those fields for you, but you need to wait for the administrator to actually export the users using the plugin and reimport it with Update existing users and Update roles for existing users? not set to No or just delete you user and reimport the CSV or simply import it into another instance with vulnerable plugin where user is not present.

plugin: https://downloads.wordpress.org/plugin/import-users-from-csv-with-meta.2.4.17.zip

Download Tool

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.

    930
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    554
  • 3

    redforge

    cybersecurity91/redforge

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

    354
  • 4

    ARTEX

    baarai/artex

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

    349
  • 5

    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.

    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.

    289

Explore all tools

Browse our collection of tools

View all tools →