How severe is GHSA-vq6j-hj8w-7v39?

GHSA-vq6j-hj8w-7v39 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vq6j-hj8w-7v39?

GHSA-vq6j-hj8w-7v39 affects the following packages: decidim-demographics (RubyGems), decidim-demographics (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-vq6j-hj8w-7v39?

Update decidim-demographics to 0.31.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vq6j-hj8w-7v39 is resolved across your whole dependency graph.

How do I detect GHSA-vq6j-hj8w-7v39 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decidim-demographics, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vq6j-hj8w-7v39 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-vq6j-hj8w-7v39 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vq6j-hj8w-7v39 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vq6j-hj8w-7v39?

GHSA-vq6j-hj8w-7v39 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vq6j-hj8w-7v39?

GHSA-vq6j-hj8w-7v39 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vq6j-hj8w-7v39 published, and has it been updated?

GHSA-vq6j-hj8w-7v39 was published on July 13, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

MEDIUM severity

Decidim: Forms admin question editor lacks authorizationGHSA-vq6j-hj8w-7v39

MEDIUMFix: decidim/decidim#16665

GHSA-vq6j-hj8w-7v39 is a medium-severity (CVSS 5.4) CWE-862 vulnerability in decidim-demographics. A fix is available for decidim-demographics — see the affected versions and patch details below.

Also known asCVE-2026-45086

Published

Jul 13, 2026

Updated

Jul 13, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vq6j-hj8w-7v39.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-vq6j-hj8w-7v39 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

💎decidim-demographics💎decidim-demographics

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

A participant can load the demographics questionnaire admin editor and make changes.

Technical description

The demographics questionnaire editor should require admin access, but the route under /admin/demographics/questions renders the editor interface without checking whether the caller is an admin. A normal participant can load the page and see the live update form action, which proves the protected interface is reachable.

Reproduction steps:

Step 1. Sign in as a normal participant: Open http://localhost:3000/users/sign_in. Step 2. Request the admin-only editor directly. Open http://localhost:3000/admin/demographics/questions/edit_questions in the same browser. Step 3. Add another question:

Note that access was denied when attempting to see question responses or settings.

Impact

Low-privilege users can access questionnaire-admin interfaces.
They can read question-management surfaces that should remain limited to questionnaire managers.

Patches

See https://github.com/decidim/decidim/pull/16665

Workarounds

Disable the "decidim-demographics" module

Reference

OWASP A01:2021 Broken Access Control

Credits

This issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`decidim-demographics`	≥ 0.31.0&&< 0.31.5	0.31.5`bundle update decidim-demographics --conservative`
💎RubyGems	`decidim-demographics`	≥ 0.32.0.rc1&&< 0.32.0	0.32.0`bundle update decidim-demographics --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decidim-demographics, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update decidim-demographics to 0.31.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vq6j-hj8w-7v39 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

## Description A participant can load the demographics questionnaire admin editor and make changes. ## Technical description The demographics questionnaire editor should require admin access, but the route under `/admin/demographics/questions` renders the editor interface without checking whether the caller is an admin. A normal participant can load the page and see the live update form action, which proves the protected interface is reachable. Reproduction steps: Step 1. Sign in as a normal participant: Open `http://localhost:3000/users/sign_in`. Step 2. Request the admin-only editor dir