CVE-2025-31696 — rapidoc_elements_field_fo…
MEDIUMCVE-2025-31696 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in drupal/rapidoc_elements_field_formatter. A fix is available for drupal/rapidoc_elements_field_formatter — see the affected versions and patch details below.
RapiDoc OAS Field Formatter - Moderately critical - Cross site scripting - SA-CONTRIB-2025-025
Exploitation Status
No confirmed exploitation observed yet
- 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-31696.
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
drupal/rapidoc_elements_field_formatterReal-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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal RapiDoc OAS Field Formatter allows Cross-Site Scripting (XSS). This issue affects RapiDoc OAS Field Formatter: from 0.0.0 before 1.0.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | drupal/rapidoc_elements_field_formatter | all versions | 1.0.1composer require drupal/rapidoc_elements_field_formatter:^1.0.1 |
Affected Products
rapidoc oas field formatterchapterthreeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/rapidoc_elements_field_formatter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/rapidoc_elements_field_formatter to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-31696 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2025-31696 in your dependencies?
Find it across Packagist, including transitive dependencies.