# CVE-2026-84924: Email Verification / SMS Verification / OTP Verification - Critical - Cross Site Scripting - SA-CONTRIB-2026-125


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** DRUPAL-CONTRIB-2026-125, GHSA-cr9m-wc8j-vr2m

## What is CVE-2026-84924?

CVE-2026-84924 is a medium-severity vulnerability in Drupal Email Verification / SMS Verification / OTP Verification, published on 22 Oct 2026. 

### Official description

Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal Email Verification / SMS Verification / OTP Verification allows Reflected XSS. This issue affects Email Verification / SMS Verification / OTP Verification versions: from 0.0.0 to 2.4.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-84924?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/otp_verification` | Packagist:https://packages.drupal.org/8 | All versions | 2.4.0 |

## How do I fix CVE-2026-84924?

Upgrade to a fixed version.

## Is CVE-2026-84924 being exploited?

There is no known exploitation of CVE-2026-84924 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84924 and fix it if it is affected.

What it is: CVE-2026-84924 is a medium-severity vulnerability in Drupal Email Verification / SMS Verification / OTP Verification, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-84924 in the wild and no public exploit code.

Affected product: Drupal Email Verification / SMS Verification / OTP Verification. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84924/ (Markdown: https://insights.sbomify.com/CVE-2026-84924/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84924
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84924
- OSV: https://osv.dev/vulnerability/CVE-2026-84924

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84924/
Summaries are generated and may contain mistakes; the official description above is the record.