Skip to content
Fencer Vulns
medium 5.7

CVE-2023-48220 json

Decidim's devise_invitable gem vulnerable to circumvention of invitation token expiry period

published 2024-02-20 2 y ago modified 2026-09-10 1 mo ago also EUVD-2024-0744 , GHSA-w3q8-m492-4pwp

cvss
5.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

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.

Patch / fix

  • rubygems decidim 0.26.9, 0.27.5
  • rubygems decidim-admin 0.26.9, 0.27.5
  • rubygems decidim-system 0.26.9, 0.27.5
  • rubygems devise_invitable 2.0.9
  • decidim decidim 0.26.9, 0.27.5, 2.0.9

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.7 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
GitHub 3.1 5.7 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
NVD 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
rubygems decidim
>=0.0.1.alpha3, <0.26.9
>=0.27.0, <0.27.5
0.26.9
0.27.5
rubygems decidim-admin
>=0.0.1.alpha3, <0.26.9
>=0.27.0, <0.27.5
0.26.9
0.27.5
rubygems decidim-system
>=0.0.1.alpha3, <0.26.9
>=0.27.0, <0.27.5
0.26.9
0.27.5
rubygems devise_invitable
>=0.4.rc3, <2.0.9
2.0.9

Affected products

  • decidim decidim

Classification

Weakness
  • CWE-672 Operation on a Resource after Expiration or Release

References

Sources

Fencer Vulns 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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.