CVE-2023-48220: Decidim's devise_invitable gem vulnerable to circumvention of invitation token expiry period
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.79% (FIRST EPSS); higher than 56.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: decidim (RubyGems) 0.26.9, 0.27.5; decidim-admin (RubyGems) 0.26.9, 0.27.5; decidim-system (RubyGems) 0.26.9, 0.27.5.
Low priority for now. Upgrade to decidim (RubyGems) 0.26.9, 0.27.5; decidim-admin (RubyGems) 0.26.9, 0.27.5; decidim-system (RubyGems) 0.26.9, 0.27.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 56th percentile
- CWE
- CWE-672
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.4
- CNA · GitHub_M
- 5.7
- 1.7 point gap
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| decidim | decidim | cpe:2.3:a:decidim:decidim |
| scambra | devise invitable | cpe:2.3:a:scambra:devise_invitable |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- decidim decidim0.0.2 and later · before 0.26.9
- decidim decidim0.27.0 and later · before 0.27.5
- decidim decidim0.0.1
- scambra devise invitable0.4.1 and later · before 2.0.9
- scambra devise invitable0.4.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
decidim decidim
- >= 0.0.1.alpha3, < 0.26.9, >= 0.27.0, < 0.27.5, >= 0.4.rc3, < 2.0.9affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| RubyGems | decidim | from 0.0.1.alpha3 · before 0.26.9 | 0.26.9 |
| RubyGems | decidim | from 0.27.0 · before 0.27.5 | 0.27.5 |
| RubyGems | decidim-admin | from 0.0.1.alpha3 · before 0.26.9 | 0.26.9 |
| RubyGems | decidim-admin | from 0.27.0 · before 0.27.5 | 0.27.5 |
| RubyGems | decidim-system | from 0.0.1.alpha3 · before 0.26.9 | 0.26.9 |
| RubyGems | decidim-system | from 0.27.0 · before 0.27.5 | 0.27.5 |
| RubyGems | devise_invitable | from 0.4.rc3 · before 2.0.9 | 2.0.9 |
Same product
decidim: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-23891Decidim has a Cross-site scripting (XSS) vulnerability via user name field37Monitor
- CVE-2026-45414Decidim: JWT-backed authentication can be replayed across organizations34Monitor
- CVE-2025-65017Decidim's private data exports can lead to data leaks32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-36465Oct 6, 2023 · Decidim has broken access control in templates28Monitor
- ← EarlierCVE-2023-47635Feb 20, 2024 · Decidim vulnerable to possible CSRF attack at questionnaire templates preview22Monitor
- Later →CVE-2023-51447Feb 20, 2024 · Decidim vulnerable to cross-site scripting (XSS) in the dynamic file uploads21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| RubyGems:decidim | 0.26.9 | Package registry (OSV) |
| RubyGems:decidim | 0.27.5 | Package registry (OSV) |
| RubyGems:decidim-admin | 0.26.9 | Package registry (OSV) |
| RubyGems:decidim-admin | 0.27.5 | Package registry (OSV) |
| RubyGems:decidim-system | 0.26.9 | Package registry (OSV) |
| RubyGems:decidim-system | 0.27.5 | Package registry (OSV) |
| RubyGems:devise_invitable | 2.0.9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-672 · Operation on a Resource after Expiration or ReleaseCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/decidim/decidim/commit/073e60e2e4224dd81815a784002ebba30f2ebb34
- github.com/decidim/decidim/commit/b12800717a689c295a9ea680a38ca9f823d2c454
- github.com/decidim/decidim/releases/tag/v0.26.9
- github.com/decidim/decidim/releases/tag/v0.27.5
- github.com/decidim/decidim/releases/tag/v0.28.0
- github.com/decidim/decidim/security/advisories/GHSA-w3q8-m492-4pwp
- github.com/scambra/devise_invitable/blob/41f58970ff76fb64382a9b9ea1bd530f7c3adab2/lib/devise_invitable/models.rb#L198
- github.com/scambra/devise_invitable/commit/94d859c7de0829bf63f679ae5dd3cab2b866a098
Vendor advisories and official records. Exploit/PoC links are deliberately left out.