CVE-2023-48220
No exploitation reported by the sources we read.
- Published2024-02-20
- Fixed in2.0.9 · 0.27.5 · 0.26.9
- WeaknessCWE-672
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Decidim is a participatory democracy framework. Starting in version 0.4.rc3 and prior to version 2.0.9 of the `devise_invitable` gem, the invites feature allows users to accept the invitation for an unlimited amount of time through the password reset functionality. This issue creates vulnerable dependencies starting in version 0.0.1.alpha3 and prior to versions 0.26.9, 0.27.5, and 0.28.0 of the `decidim,` `decidim-admin`, and `decidim-system` gems. When using the password reset functionality, the `devise_invitable` gem always accepts the pending invitation if the user has been invited. The only check done is if the user has been invited but the code does not ensure that the pending invitation is still valid as defined by the `invite_for` expiry period. Decidim sets this configuration to `2.weeks` so this configuration should be respected. The bug is in the `devise_invitable` gem and should be fixed there and the dependency should be upgraded in Decidim once the fix becomes available. `devise_invitable` to version `2.0.9` and above fix this issue. Versions 0.26.9, 0.27.5, and 0.28.0 of the `decidim,` `decidim-admin`, and `decidim-system` gems contain this fix. As a workaround, invitations can be cancelled directly from the database.
Timeline
dates in UTC- 2024-02-2018:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-48220?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-48220?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
CISA-ADP · OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.0 | ≥ 0.4.rc3, < 2.0.9 | 2.0.9 | CISA-ADP · OSV |
| 0.27 | ≥ 0.27.0, < 0.27.5 | 0.27.5 | NVD · CISA-ADP · OSV |
| 0.x | ≥ 0.0.2, < 0.26.9 | 0.26.9 | NVD |
| 0.x | ≥ 0.0.1.alpha3, < 0.26.9 | 0.26.9 | CISA-ADP · OSV |
| 0.0 | = 0.0.1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.0 | ≥ 0.4.1, < 2.0.9 | 2.0.9 | NVD |
| 0.4 | = 0.4.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Decidim to 2.0.9 · 0.27.5 · 0.26.9
Advisories and patches
- github.comPatch
- github.comPatch
- github.comRelease Notes
- github.comRelease Notes
- github.comRelease Notes
- github.comMitigation · Patch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Published
- 2024-02-20
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2023-48220?
Is CVE-2023-48220 actively exploited?
What is the CVSS score for CVE-2023-48220?
Running decidim? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.