CVE-2025-31686 is a high-severity (CVSS 8.1) CWE-862 vulnerability in goalgorilla/open_social. A fix is available for goalgorilla/open_social — see the affected versions and patch details below.
Open Social - Less critical - Access bypass, Information Disclosure - SA-CONTRIB-2025-015
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-31686.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
goalgorilla/open_social🐘goalgorilla/open_socialReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Missing Authorization vulnerability in Drupal Open Social allows Forceful Browsing. This issue affects Open Social: from 0.0.0 before 12.3.11, from 12.4.0 before 12.4.10.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | goalgorilla/open_social | all versions | 12.3.11composer require goalgorilla/open_social:^12.3.11 |
| 🐘Packagist | goalgorilla/open_social | ≥ 12.4.0&&< 12.4.10 | 12.4.10composer require goalgorilla/open_social:^12.4.10 |
Affected Products
open socialgetopensocialDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for goalgorilla/open_social, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update goalgorilla/open_social to 12.3.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-31686 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
Is CVE-2025-31686 in your dependencies?
Find it across Packagist, including transitive dependencies.