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-122158 — Analysis and loopback-restricted PoC for CVE-2026-122158, a cross-tenant privilege escalation in InvoiceShelf allowing an owner to assign arbitrary roles in another tenant. | Kitploit
Tools/GitHubGitHub/capivara-research/cve-2026-122158
Privilege EscalationVulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPapers & ResearchLabs & Practice
GitHubcapivara-research/cve-2026-122158

CVE-2026-122158

Analysis and loopback-restricted PoC for CVE-2026-122158, a cross-tenant privilege escalation in InvoiceShelf allowing an owner to assign arbitrary roles in another tenant.

View Repository
14 days agoNot yet reviewed
Share

CVE-2026-122158 — InvoiceShelf cross-tenant privilege escalation

CVE-2026-122158 — InvoiceShelf cross-tenant privilege escalation

CVE VulDB VulDB Submit

A company owner can place an attacker-controlled account into another tenant with an arbitrary role, including owner.

Português do Brasil · Official advisory · Fix for 2.x · Fix for 3.x

VulDB accepted submission #1028117, created VDB-431158, and assigned CVE-2026-122158. The canonical CVE record was published on November 5, 2026.

At a glance

ItemValue
ProductInvoiceShelf
Affected<= 2.4.3; 3.0.0-alpha.1 through 3.0.0-alpha.3
Fixed2.4.4; 3.0.0-alpha.4
GHSA severityCritical
WeaknessCWE-284, CWE-863 (GHSA); CWE-284, CWE-266 (CVE)
VulDB CVSS v3.14.7 — CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C
Researcher CVSS v3.19.1 — CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
AdvisoryGHSA-c9cx-7r7m-264v
CVECVE-2026-122158
VulDBVDB-431158

Why this happens

MemberRequest validates only the shape of the client-controlled companies array. It does not establish that the caller owns the referenced company or may assign the requested role:

'companies' => ['required'],
'companies.*.id' => ['required'],
'companies.*.role' => ['required'],

MemberService::create() and update() then treat that list as authoritative. They synchronize memberships using the supplied IDs and switch Bouncer's authorization scope to each supplied company before assigning the supplied role:

$member->companies()->sync($memberships->pluck('id'));

foreach ($memberships as $membership) {
    BouncerFacade::scope()->to($membership['id']);
    BouncerFacade::sync($member)->roles([$membership['role']]);
}

The controller verifies that the caller owns the active company. It does not bind that authorization decision to companies[].id in the request body. This creates a confused authorization boundary:

owner of Company A
        │ authorized to create a member in A
        ▼
POST /api/v1/members
companies[0].id = Company B
companies[0].role = owner
        │ values trusted by the service
        ▼
attacker-controlled account becomes an owner of Company B

Proof of concept

The repository deliberately provides a laboratory-only reproducer. It refuses non-loopback targets and does nothing unless --execute is supplied. We did not execute it while preparing this disclosure.

Prerequisites:

  1. An isolated InvoiceShelf 2.4.3 or 3.0.0-alpha.3 test installation.
  2. Two test companies, A and B.
  3. A valid Sanctum token for an owner of Company A.
  4. The numeric identifier of Company B.

Preview the request without sending it:

python3 poc/poc.py \
  --base-url http://127.0.0.1:8080 \
  --token LAB_TOKEN \
  --active-company-id 1 \
  --victim-company-id 2 \
  --email [email protected]

After reviewing the generated request, an authorized tester can add --execute. On a vulnerable release, the expected vulnerable result is HTTP 200/201 and a new member associated with Company B as owner. A fixed release must reject the cross-company membership, normally with HTTP 403 or 422, and must not create the unauthorized relationship.

See poc/poc.py and poc/request.http.

Impact

An owner of one legitimate tenant can obtain administrative control over another tenant on the same installation. The resulting account can access or alter invoices, customers, payments and other financial records, invite additional users, and exercise any capability granted to the selected role. Confidentiality, integrity and availability cross the intended tenant boundary.

VulDB scores the issue as Medium (4.7) with unchanged scope and Low impact to confidentiality, integrity, and availability. The public GHSA rates it Critical, while the researcher vector models the administrative cross-tenant boundary as changed scope with High impact. These are different risk models for the same root cause; consumers should apply the vector that matches their deployment and vulnerability-management policy.

Remediation

Upgrade to 2.4.4, 3.0.0-alpha.4, or a later release. The fix restricts submitted company IDs to companies owned by the caller, validates roles in their company scope, preserves memberships outside the caller's authority, and prevents sensitive account changes when a member also belongs to a company the caller does not own.

Disclosure and references

  • CVE-2026-122158 — canonical CVE Program record
  • VDB-431158 — VulDB entry
  • Public GitHub Security Advisory
  • VulDB submission #1028117
  • InvoiceShelf repository
  • Patch for the 2.x line, PR #826
  • Patch for the 3.x line, PR #822
  • Audited commit: 0076ab9c5b1840d53690e721a1a4e7a91a068795
  • Public disclosure: 2026-09-23

Timeline

DateEvent
2026-09-16InvoiceShelf commit 0076ab9c5b1840d53690e721a1a4e7a91a068795 audited
2026-09-23Vendor published GHSA-c9cx-7r7m-264v and credited capivara-research as reporter
2026-11-04VulDB accepted submission #1028117, created VDB-431158, and reserved CVE-2026-122158
2026-11-05The canonical CVE record was published

Credits

Research and disclosure credits:

  • Alysson Dutra
  • Lucas Diniz
  • Fernando Viana

The public GHSA currently lists capivara-research as Reporter and gdarko as Coordinator.

Legal and ethical use

Use this material only on systems you own or have explicit permission to test. The reproducer is constrained to loopback laboratory targets. Do not test public or third-party InvoiceShelf installations.

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.

    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 →