CVE-2025-13980 json
CKEditor 5 Premium Features - Moderately critical - Access bypass - SA-CONTRIB-2025-118
published 11mo ago modified 2mo ago also DRUPAL-CONTRIB-2025-118 , EUVD-2025-206441
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal CKEditor 5 Premium Features allows Functionality Bypass.This issue affects CKEditor 5 Premium Features: from 0.0.0 before 1.2.10, from 1.3.0 before 1.3.6, from 1.4.0 before 1.4.3, from 1.5.0 before 1.5.1, from 1.6.0 before 1.6.4.
Patch / fix
- packagist drupal/ckeditor5_premium_features 1.2.10, 1.3.6, 1.4.3, 1.5.1, 1.6.4
- Drupal CKEditor 5 Premium Features 1.2.10, 1.3.6, 1.4.3, 1.5.1, 1.6.4
Is CVE-2025-13980 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 9mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | drupal/ckeditor5_premium_features | <1.2.10 >=1.3.0, <1.3.6 >=1.4.0, <1.4.3 >=1.5.0, <1.5.1 >=1.6.0, <1.6.4 |
1.2.10 1.3.6 1.4.3 1.5.1 1.6.4 |
Affected products
- Drupal CKEditor 5 Premium Features
Classification
- Weakness
-
- CWE-288 Authentication Bypass Using an Alternate Path or Channel
References
-
drupal.org
/sa-contrib-2025-118
vendor-advisory, web
Sources
- CVE List CVE-2025-13980
- NVD CVE-2025-13980
- OSV DRUPAL-CONTRIB-2025-118
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.