Skip to content
KitploitKITPLOIT
उपकरणएक्सप्लॉइटब्लॉग
Log in
जमा करें
उपकरणएक्सप्लॉइटब्लॉग
जमा करें

हैकिंग, पेनटेस्ट और साइबर सुरक्षा उपकरण आपके सुरक्षा शस्त्रागार के लिए!

Kitploit हैकिंग, साइबर सुरक्षा और पेंटेस्टिंग टूल्स की एक निर्देशिका है। कमजोरियों को खोजने, सिस्टम का विश्लेषण करने, परीक्षण को स्वचालित करने और अपनी सुरक्षा को मजबूत करने के लिए नवीनतम प्रोजेक्ट अपडेट खोजें।

फ़ीडसंपर्कगोपनीयता© 2026 Kitploit

टूल निर्देशिका

श्रेणियाँ

सभी श्रेणियाँ देखें
Loading categories
CVE-2026-121529 — Containerised proof-of-concept for CVE-2026-121529, a FortiClient local API origin validation error (CWE-346) enabling drive-by RCE, with a real-browser differential across four remediation models. | Kitploit
उपकरण/GitHubGitHub/googlesky/cve-2026-121529
Container SecurityVulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityRed Teaming
GitHubgooglesky/cve-2026-121529

CVE-2026-121529

Containerised proof-of-concept for CVE-2026-121529, a FortiClient local API origin validation error (CWE-346) enabling drive-by RCE, with a real-browser differential across four remediation models.

रिपॉजिटरी देखें
1 दिन पहलेअभी तक समीक्षित नहीं
साझा करें
अनुरोधित भाषा में सामग्री उपलब्ध नहीं है। अंग्रेज़ी संस्करण दिखाया जा रहा है।

CVE-2026-121529 — FortiClient local API origin validation error (drive-by RCE)

CVECVE-2026-121529
ComponentFortiClient / FortiClient Windows PAM / FortiClient Mac — local API endpoint (127.0.0.1:9191)
AffectedWindows & Windows PAM 7.4.0–7.4.7, 7.2.0–7.2.14; Mac 7.4.0–7.4.7
Fixed in7.4.8 (7.4 branch), 7.2.15 (7.2 branch)
CWECWE-346 (Origin Validation Error)
ImpactUnauthenticated remote code execution as the FortiClient service account (SYSTEM on Windows)
VectorA web page the victim visits; the victim's own browser drives the privileged local API
TriggerThe Origin header of a cross-origin request — or its absence

Fortinet's advisory (FG-IR-26-194, published 2026-11-10) describes the flaw as an origin validation error in the local API of FortiClient, FortiClient Windows PAM and FortiClient Mac that "may allow an unauthorized remote attacker to execute unauthorized code or commands" and requires interaction with the victim.

The local API is the loopback interface used by the FortiPAM privileged-access components on the same endpoint. It listens on 127.0.0.1:9191 and offers a privileged-session operation that runs a command with the privileges of the service. Because the service never validates the origin of the caller, a page on any web site can make the victim's own browser drive that API: the browser sends the request, the API executes it, and the browser hands the answer back to the attacker's script. The victim only has to visit a page.

This repository contains a containerised laboratory that reproduces the flaw with a real browser, the differential against three remediation shapes, and the results of a 0-day sweep against the patched model. The sweep produces three findings that matter for any product of this shape: a CORS-header-only remediation does not stop the attack at all, because a browser applies no CORS policy to a WebSocket handshake; an origin-validated remediation that accepts a request without an Origin header is bypassed by a cross-origin ``; and a blind execution can be confirmed through an image side channel.


1. Scope and fidelity of this laboratory

FortiClient is proprietary software. None of its code, binaries or configuration are redistributed here, and the vendor does not publish the local API's endpoint list or its origin-validation code. What is reproducible here is therefore:

  • the vendor's own statement of the defect — CWE-346, local API endpoint, unauthenticated, victim interaction required, CVSS 9.1, and the affected/fixed version matrix — taken verbatim from FG-IR-26-194;
  • the security-relevant behaviour of the local API — a loopback HTTP listener on 127.0.0.1:9191, a privileged-session operation that executes a command with the service's privileges, a WebSocket variant of that operation, and an origin-validation layer;
  • the browser-side semantics that turn the origin-validation error into code execution. These are properties of the browser and of the HTTP/CORS protocol, not of FortiClient, and they are exercised with a real Chromium instance.

Everything the laboratory asserts about the vendor product is sourced from the advisory; everything it asserts about the model is labelled as such. The model is the only thing that runs in the lab, and it is deliberately built so that the vulnerable and the patched behaviour differ in the origin-validation layer alone.

The model lives in lab/forticlient_api.py and is selected with FCT_MODE:

FCT_MODEbehaviourversion reported
vulnno origin validation at all — the request Origin is reflected into Access-Control-Allow-Origin together with Access-Control-Allow-Credentials: true7.4.7
fixed-corsremediation that only tightens the CORS headers; the request is still processed, and the WebSocket surface is not covered by CORS at all7.4.8
fixed-origin-onlyremediation that validates the origin server-side but still accepts a request that carries no Origin header7.4.8
fixed-strictremediation that validates the origin server-side and requires a shared secret header that a cross-origin request cannot set without a preflight7.4.8

2. Root cause

The browser — not the server — decides whether a page may read the answer of a cross-origin request. The server expresses that decision in the CORS response headers: Access-Control-Allow-Origin names the single origin that is allowed to read the response, and Access-Control-Allow-Credentials: true additionally allows the request to carry cookies and other credentials.

A local API that reflects the request's own Origin back into that header, and pairs it with Access-Control-Allow-Credentials: true, hands every page on the internet a valid cross-origin channel into a privileged local service. The origin is never validated, and CWE-346 is exactly that: the server trusts the value it is supposed to check.

The vulnerable model does this in _send():

origin = cors_origin if cors_origin is not None else self.headers.get("Origin")
if cors_allowed(origin) and origin:
    # The vulnerable build echoes ANY origin and allows credentials.
    self.send_header("Access-Control-Allow-Origin", origin)     # <-- any origin
    self.send_header("Access-Control-Allow-Credentials", "true")

and cors_allowed() in the vuln mode returns True for every input:

def cors_allowed(origin):
    if MODE == "vuln":
        # 7.4.7 model: the service trusts whatever origin asks.
        return True

The preflight is equally permissive, and it reflects the requested headers as well:

def do_OPTIONS(self):
    ...
    extra = {
        "Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, OPTIONS",
        "Access-Control-Allow-Headers": self.headers.get(
            "Access-Control-Request-Headers", "Content-Type, Authorization"),
        "Access-Control-Max-Age": "86400",
    }

The privileged operation itself performs no authorization at all — in the vuln mode action_allowed() returns True unconditionally — so the request that arrives with a forged or absent origin is executed with the privileges of the service:

def action_allowed(headers):
    if MODE in ("vuln", "fixed-cors"):
        return True

The patched shape

A remediation has to decide on the server whether the caller is a trusted local component. The fixed-strict model does that before the action is performed:

def action_allowed(headers):
    ...
    origin = headers.get("Origin")
    token  = headers.get(TOKEN_HEADER)
    if token != TOKEN:
        return False
    if origin is None:
        return True          # the native local agent sends no Origin
    return origin in ALLOWED_ORIGINS

The order matters: the check happens before the command runs, so an untrusted request never reaches the sink.


3. Attack surface

टूल डाउनलोड करें

सबसे लोकप्रिय

सभी देखें →

हमारे समुदाय द्वारा सबसे अधिक उपयोग किए जाने वाले उपकरण खोजें।

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 अंतिम OSINT टूलकिट: जाँच ग्राफ़, विश्वास स्कोरिंग, उपनाम परिवार, मानचित्र, टाइमलाइन और रिपोर्ट। 49 मॉड्यूल, 400+ साइटें, किसी API कुंजी की आवश्यकता नहीं।

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # घोस्टलॉक वन-टैप निष्पादन ऐप (CVE-2026-43499)

    593
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT प्लेटफ़ॉर्म जो Shadowserver रिपोर्ट्स को MongoDB में इनजेस्ट करता है और उन्हें इंटरैक्टिव मैप्स, विश्लेषण, निष्कर्षों, सलाहों और कार्यकारी डैशबोर्ड के रूप में पुनः प्रस्तुत करता है।

    371
  • 4

    redforge

    cybersecurity91/redforge

    ब्राउज़र-साइड रेड टीम टूलकिट, जिसमें रेकॉन, पेलोड जनरेशन, क्रेडेंशियल हमलों, क्रिप्टो, एन्कोडिंग और एंगेजमेंट रिपोर्टिंग के लिए 102 ऑफ़लाइन टूल्स हैं।

    336
  • 5

    ARTEX

    baarai/artex

    प्लानर/वर्कर एजेंट, एसेट और एक्सप्लोरेशन ग्राफ़, MITM ट्रैफ़िक रिकॉर्डिंग, और भेद्यता पुनःपरीक्षण के साथ LLM मल्टी-एजेंट स्वायत्त पेनेट्रेशन टेस्टिंग प्लेटफ़ॉर्म।

    326
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI-मूल साइबरसुरक्षा के लिए कार्रवाई की प्रणाली—जहाँ इरादा नियंत्रित निष्पादन बन जाता है, साक्ष्य परिचालन स्मृति बन जाता है, और हर ऑपरेशन अगले को बेहतर बनाता है।

    322

सभी उपकरण खोजें

हमारे उपकरणों का संग्रह ब्राउज़ करें

सभी उपकरण देखें →