Detect PraisonAI Platform JWT Hardcoded Secret Key Token Forgery in Google Chronicle
Detects exploitation of CVE-2026-47410, a critical vulnerability in praisonai-platform (<= 0.1.2) where the JWT signing key defaults to the hardcoded value 'dev-secret-change-me' when PLATFORM_ENV is unset. An unauthenticated attacker can forge valid JWTs for any user, including administrators, enabling full platform compromise.
MITRE ATT&CK
YARA-L Detection Query
rule cve_2026_47410_jwt_hardcoded_key_forgery {
meta:
author = "df00tech Detection Engineering"
description = "Detects potential exploitation of CVE-2026-47410 praisonai-platform JWT hardcoded secret"
severity = "CRITICAL"
priority = "HIGH"
reference = "https://github.com/advisories/GHSA-3qg8-5g3r-79v5"
events:
$http.metadata.event_type = "NETWORK_HTTP"
$http.network.http.method = /POST|PUT|DELETE|PATCH|GET/
$http.network.http.request_headers["authorization"] = /Bearer\s+[A-Za-z0-9+\/=._-]+/
(
$http.network.http.target_url = /\/api\// or
$http.network.http.target_url = /\/admin\// or
$http.network.http.target_url = /\/auth\//
)
$http.principal.ip = $ip
match:
$ip over 10m
outcome:
$request_count = count_distinct($http.network.http.target_url)
$risk_score = if($request_count > 5, 90, if($request_count > 2, 70, 50))
condition:
#http > 3 and $request_count > 1
}Chronicle YARA-L rule detecting multi-endpoint JWT-authenticated access patterns indicative of token forgery exploitation of the praisonai-platform hardcoded secret vulnerability.
Data Sources
Required Tables
False Positives & Tuning
- Automated monitoring tools making authenticated requests across multiple endpoints
- Legitimate multi-step API workflows initiated by admin users
- Internal microservices communicating via JWT across praisonai-platform endpoints
- Security testing engagements with authorized scope covering admin APIs
Other platforms for CVE-2026-47410
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Forge Admin JWT Using Hardcoded Dev Secret
Expected signal: Python3 process execution with inline code containing 'dev-secret-change-me' string; no network activity generated by this step alone.
- Test 2Use Forged Admin JWT Against praisonai-platform API
Expected signal: Network connection from test host to praisonai-platform port 8000; HTTP GET request with Authorization: Bearer header visible in access logs; HTTP 200 response to admin-only /api/users/ endpoint.
- Test 3Enumerate and Escalate via Forged JWT in Headless Environment
Expected signal: Multiple sequential HTTP requests to distinct admin endpoints within seconds from same source IP; all authenticated with the same Bearer token; successful 200 responses to admin-restricted paths.
Unlock Pro Content
Get the full detection package for CVE-2026-47410 including response playbook, investigation guide, and atomic red team tests.