Security readout for executives and security teams
Plain-English summary
PraisonAI Platform before 0.1.4 can use a public, hardcoded JWT signing secret when production deployments leave key settings unset. That can let an unauthenticated attacker create valid-looking login tokens and impersonate existing users, including owners or admins. Treat exposed deployments as urgent authentication-bypass risk.
Executive priority
Prioritize remediation immediately for any deployed PraisonAI Platform instance. This is a critical authentication control failure that can enable full account impersonation without credentials when insecure defaults are present.
Technical view
The platform defaults PLATFORM_JWT_SECRET to "dev-secret-change-me" when unset. The safety check is bypassed when PLATFORM_ENV remains at its default "dev" value. In affected versions, this enables JWT forgery with arbitrary identity claims against deployments using the insecure defaults. Version 0.1.4 patches the issue.
Likely exposure
Highest exposure is PraisonAI Platform versions below 0.1.4 deployed with PLATFORM_JWT_SECRET unset, especially when PLATFORM_ENV is also unset or left as dev. Internet-facing or shared workspace deployments are most concerning because compromise maps directly to user and admin impersonation.
Exploitation context
The CVE bundle reports no CISA KEV listing and provides no cited evidence of active exploitation. The issue is still high risk because the weak secret is public source information, requires no prior account, and has low attack complexity.
Researcher notes
Mapped weaknesses are CWE-321 and CWE-798. CVSS is 9.8 under AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Evidence supports affected versions below 0.1.4 and a patch in 0.1.4, but not active exploitation.
Mitigation direction
- Upgrade PraisonAI Platform to version 0.1.4 or later.
- Set a strong, unique PLATFORM_JWT_SECRET in every deployment.
- Explicitly configure PLATFORM_ENV appropriately for production.
- Rotate JWT secrets after remediation and invalidate existing sessions if feasible.
- Review vendor advisory, PR, and commit notes for deployment-specific guidance.
Validation and detection
- Inventory PraisonAI Platform versions and flag anything below 0.1.4.
- Check runtime configuration for unset or default PLATFORM_JWT_SECRET.
- Confirm production deployments are not relying on default PLATFORM_ENV behavior.
- Review authentication logs for unexpected admin or workspace-owner activity.
- Verify patched behavior in staging before promoting to production.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-321: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-47410 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-3qg8-5g3r-79v5CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/MervinPraison/PraisonAI/pull/1685CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/MervinPraison/PraisonAI/commit/ef79b7a0561796ad9807f0f09538c25cc78d3619CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.