CVE-2026-18985
CVE-2026-18985 is a CWE-863 vulnerability in drupal/edit_in_place_field. O3 Security confirms whether CVE-2026-18985 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
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-2026-18985.
Real-World Exposure
drupal/edit_in_place_fieldReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist:https://packages.drupal.org/8 packages — download data is not available via public APIs for these ecosystems.
Description
This module provides formatters to allow in-place editing in a View or other display (full content, teaser...).
The module doesn't sufficiently check access when editing entities. A malicious user could craft requests to allow them to modify any field on any entity.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "edit in place field editing permission".
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Packagist:https://packages.drupal.org/8 | drupal/edit_in_place_field | all versions | 2.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/edit_in_place_field. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update drupal/edit_in_place_field to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-18985 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-18985 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-18985. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-18985 in your dependencies?
O3 detects CVE-2026-18985 across Packagist:https://packages.drupal.org/8 dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.