Issabel Framework Hard-coded JWT Key RCE via pbxapi/manager/originate
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Issabel Foundation | Issabel Framework | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Issabel Foundation | Issabel Framework |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 2.7% (2.699% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Issabel Foundation
Issabel Foundation issabel Framework |
|
| Vendors & Products |
Issabel Foundation
Issabel Foundation issabel Framework |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Issabel Framework, the web framework supporting Issabel PBX software, before commit b97dbaf contains a hard-coded HS256 JWT signing key in the pbxapi index.php file that is identical across every installation, allowing unauthenticated remote attackers to forge valid bearer tokens. Attackers can use the forged token to call the manager originate endpoint with the System application parameter, causing Asterisk to execute arbitrary OS commands as the Asterisk user. Exploitation evidence was first observed by the Shadowserver Foundation on 2026-09-09. | |
| Title | Issabel Framework Hard-coded JWT Key RCE via pbxapi/manager/originate | |
| Weaknesses | CWE-321 | |
| References |
| |
| Metrics |
cvssV3_1
|