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/aj2108/cve-2026-8237
Authentication & AuthorizationVulnerability AnalysisWeb Application ExploitationWeb SecurityLearning & Education
GitHubaj2108/cve-2026-8237

CVE-2026-8237

In-depth IDOR write-up for Concrete CMS, covering the message_detail endpoint, missing authorization root cause, attack scenarios, impact, and fix.

View Repository
473 months agoNot yet reviewed
Share

CVE-2026-8237

CVE-2026-8237 is an Insecure Direct Object Reference (IDOR) vulnerability caused by missing authorization checks in Concrete CMS 9.5.0 and earlier.The flaw exists in the /ccm/frontend/conversations/message_detail endpoint, which returns the full contents of conversation messages based solely on a user-supplied message identifier. Because the application does not verify whether the requester is authorized to access the specified message, an unauthenticated attacker can enumerate message IDs and retrieve conversation content that should remain private. File attachment download URLs associated with those messages may also be disclosed. The issue is fixed in Concrete CMS 9.5.1.

Affected Software

Property Value
Product Concrete CMS
Affected Versions 9.5.0 and earlier
Fixed Version 9.5.1
Affected Endpoint /ccm/frontend/conversations/message_detail

Vulnerability Type

  • Category: Insecure Direct Object Reference (IDOR)

  • CWE-862: Missing Authorization

Root Cause

The endpoint retrieves a conversation message using a client-controlled message ID without validating whether the current user has permission to access that specific message.

The vulnerable workflow is conceptually:

User supplies messageId
↓
Server fetches message
↓
No authorization check
↓
Returns full message content

Because ownership or access permissions are never verified, attackers can change the messageId value to access other users' conversation messages.

Attack Scenario

Assume a legitimate request retrieves message 150:

GET /ccm/frontend/conversations/message_detail?messageId=150

An attacker simply changes the identifier:

GET /ccm/frontend/conversations/message_detail?messageId=151

If the server responds with the contents of message 151 instead of denying access, the attacker can continue incrementing IDs to enumerate private conversations and their associated attachments.

Impact

Successful exploitation may allow an attacker to:

  • Read private conversation messages.
  • Access discussions from restricted or members-only pages.
  • View moderation queue messages.
  • Obtain file attachment download URLs.
  • Enumerate valid conversation message IDs.

The vulnerability primarily impacts confidentiality because sensitive information can be disclosed without authorization.

Severity

Metric Score
CVSS v3.1 (NVD) 5.3 (Medium)
CVSS v4.0 (Concrete CMS) 6.3 (Medium)

Conceptual Vulnerable Code

Note: The vendor has not published the actual vulnerable source code. The following example illustrates the vulnerability pattern only.

$messageId = $_GET['messageId'];

$message = $conversationRepository->find($messageId);

// Missing authorization check
return response()->json([
    'message' => $message->getContent(),
    'attachments' => $message->getAttachments()
]);

Why It Is Vulnerable

The application trusts the user-controlled messageId and returns the requested message without confirming that the requester is authorized to access it.

Corrected Code (Conceptual)

$messageId = $_GET['messageId'];

$message = $conversationRepository->find($messageId);

if (!$authorizationService->canView($currentUser, $message)) {
    return response()->json([
        'error' => 'Access denied'
    ], 403);
}

return response()->json([
    'message' => $message->getContent(),
    'attachments' => $message->getAttachments()
]);

Why This Fix Works

The corrected implementation performs a server-side authorization check before returning any conversation data. Even if an attacker modifies the messageId, the request is denied unless the user has permission to access that specific message. This prevents unauthorized disclosure of conversation contents and attachments.

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.

    565
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    478
  • 3

    ARTEX

    baarai/artex

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

    383
  • 4

    redforge

    cybersecurity91/redforge

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

    327
  • 5

    estorides

    grisuno/estorides

    Aggregates 99+ free OSINT sources in parallel, resolves entities into a knowledge graph, and exports STIX 2.1, MISP, or GraphML with LLM-assisted analysis.

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

    256

Explore all tools

Browse our collection of tools

View all tools →