Description
Improper Neutralization of Input During Web Page Generation (XSS) vulnerability in team-alembic AshAuthentication allows reflected cross-site scripting via the confirmation and magic link interaction forms.

When a strategy is configured with require_interaction? set to true, AshAuthentication serves an intermediate HTML page asking the user to confirm the action by submitting a form. Both such pages embed a request parameter directly into a hidden input's value attribute without HTML escaping: lib/ash_authentication/add_ons/confirmation/confirmation_form.html.eex interpolates the confirm parameter, and lib/ash_authentication/strategies/magic_link/sign_in_form.html.eex interpolates the magic link token parameter. These templates are compiled with EEx.function_from_file/3 using plain <%= %> expressions, which perform no escaping, so the parameter is reflected verbatim.

Neither accept handler validates the value before rendering it. AshAuthentication.AddOn.Confirmation.Plug.accept/2 only checks that a confirm key is present, and AshAuthentication.Strategy.MagicLink.Plug.accept/2 reads the parameter directly, so no token signature is verified at this stage and arbitrary attacker-supplied text reaches the template. An unauthenticated attacker can therefore craft a URL whose parameter terminates the attribute and injects markup, for example a quote followed by a <script> element. Because the accept phase is served over GET, loading the crafted link is sufficient; no form submission or prior authentication is required.

The injected script executes in the origin of the application embedding AshAuthentication, giving it access to that origin's cookies, session, and same-origin responses. Since these pages are part of the authentication flow, a victim following what appears to be a legitimate confirmation or sign-in link is a plausible target.

This issue affects ash_authentication: from 4.8.0 before 4.14.2 and from 5.0.0-rc.0 before 5.0.0-rc.13.
Published: 2026-08-25
Score: 2.1 Low
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a reflected Cross‑Site Scripting flaw in AshAuthentication. Templates that render confirmation and magic‑link forms do not escape a request parameter into a hidden input, allowing an attacker to inject arbitrary HTML or JavaScript. The injected code runs with the same origin as the application, so an attacker can read session cookies, hijack sessions, or perform other client‑side attacks against a victim following a seemingly legitimate link.

Affected Systems

The flaw affects the team‑alembic AshAuthentication library in releases from 4.8.0 up to but excluding 4.14.2, and from 5.0.0‑rc.0 up to but excluding 5.0.0‑rc.13. The vulnerability has been observed in applications that embed the library with a configuration option require_interaction? set to true.

Risk and Exploitability

The CVSS score of 2.1 indicates a low severity, and the EPSS score is not available; the vulnerability is not listed in CISA’s KEV catalog. Nevertheless, exploitation only requires an unauthenticated attacker to craft a malicious URL and entice a user to click it, which is a common social engineering scenario. Because the injected script executes in the app’s origin context, the impact can be significant if the user is logged in or has a valid session cookie. Given the lack of additional authentication checks during the GET request, the attack vector is considered low barrier but high potential impact on affected users.

Generated by OpenCVE AI on August 25, 2026 at 09:22 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade AshAuthentication to version 4.14.2 or later or 5.0.0‑rc.13 or later, which contains the input‑validation fix.
  • If an upgrade is not immediately possible, patch the confirmation and magic‑link templates to escape the confirm and magic link token parameters or validate them before rendering them in hidden inputs.
  • Monitor your application for anomalous GET requests containing unexpected script payloads and consider implementing a web‑application firewall to block known XSS patterns.

Generated by OpenCVE AI on August 25, 2026 at 09:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 25 Aug 2026 08:15:00 +0000

Type Values Removed Values Added
Description Improper Neutralization of Input During Web Page Generation (XSS) vulnerability in team-alembic AshAuthentication allows reflected cross-site scripting via the confirmation and magic link interaction forms. When a strategy is configured with require_interaction? set to true, AshAuthentication serves an intermediate HTML page asking the user to confirm the action by submitting a form. Both such pages embed a request parameter directly into a hidden input's value attribute without HTML escaping: lib/ash_authentication/add_ons/confirmation/confirmation_form.html.eex interpolates the confirm parameter, and lib/ash_authentication/strategies/magic_link/sign_in_form.html.eex interpolates the magic link token parameter. These templates are compiled with EEx.function_from_file/3 using plain <%= %> expressions, which perform no escaping, so the parameter is reflected verbatim. Neither accept handler validates the value before rendering it. AshAuthentication.AddOn.Confirmation.Plug.accept/2 only checks that a confirm key is present, and AshAuthentication.Strategy.MagicLink.Plug.accept/2 reads the parameter directly, so no token signature is verified at this stage and arbitrary attacker-supplied text reaches the template. An unauthenticated attacker can therefore craft a URL whose parameter terminates the attribute and injects markup, for example a quote followed by a <script> element. Because the accept phase is served over GET, loading the crafted link is sufficient; no form submission or prior authentication is required. The injected script executes in the origin of the application embedding AshAuthentication, giving it access to that origin's cookies, session, and same-origin responses. Since these pages are part of the authentication flow, a victim following what appears to be a legitimate confirmation or sign-in link is a plausible target. This issue affects ash_authentication: from 4.8.0 before 4.14.2 and from 5.0.0-rc.0 before 5.0.0-rc.13.
Title Reflected XSS in AshAuthentication confirmation and magic link interaction forms
First Time appeared Team-alembic
Team-alembic ash Authentication
Weaknesses CWE-79
CPEs cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*
Vendors & Products Team-alembic
Team-alembic ash Authentication
References
Metrics cvssV4_0

{'score': 2.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N'}


Subscriptions

Team-alembic Ash Authentication
cve-icon MITRE

Status: PUBLISHED

Assigner: EEF

Published:

Updated: 2026-08-25T08:03:47.721Z

Reserved: 2026-07-28T04:15:10.240Z

Link: CVE-2026-66882

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-25T08:18:10.143

Modified: 2026-08-25T08:18:10.143

Link: CVE-2026-66882

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-25T09:30:05Z

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')