CVE-2026-122075 json
This module enables you to schedule content to be published or unpublished at a certain time in the future.
published 5d ago modified 5d ago also DRUPAL-CONTRIB-2026-306
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
This module enables you to schedule content to be published or unpublished at a certain time in the future.
The module doesn't sufficiently check if a user has permission to change publication or unpublication dates. This might cause certain information to be publicly disclosed ahead of the scheduled time, or content to become inaccessible earlier or later than planned.
This vulnerability is mitigated by the fact that an attacker must already have permission to edit the affected content, and the content must be editable through a web services API like JSON:API or REST.
Patch / fix
- packagist drupal/scheduler 1.7.0, 2.1.0, 2.2.0, 2.2.3, 2.3.1
Is CVE-2026-122075 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | drupal/scheduler | <1.7.0 >=2.2.0, <2.2.3 >=2.0.0, <2.1.0 >=2.1.0, <2.2.0 >=2.3.0, <2.3.1 |
1.7.0 2.2.3 2.1.0 2.2.0 2.3.1 |
References
Sources
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.