Access bypass via forced wildcard CORS
Published Jan 28, 2026 · Updated Jan 28, 2026
Permissive CORS in Drupal Next.js before 1.6.4 and 2.0.0 allows remote attackers to issue requests from any web origin. The module automatically sets Access-Control-Allow-Origin to a wildcard and overrides the site's services.yml CORS configuration without an opt-out. Every affected installation exposes the behavior; exploitation requires a user browser to load attacker-controlled web content, enabling cross-origin access to Drupal responses.
Summary
What happened
Permissive CORS in Drupal Next.js before 1.6.4 and 2.0.0 allows remote attackers to issue requests from any web origin. The module automatically sets Access-Control-Allow-Origin to a wildcard and overrides the site's services.yml CORS configuration without an opt-out. Every affected installation exposes the behavior; exploitation requires a user browser to load attacker-controlled web content, enabling cross-origin access to Drupal responses.
The record
- CVE
- CVE-2025-13984
- Published
- Jan 28, 2026
- Updated
- Jan 28, 2026
- Vendor
- Avatar Uploader Project
- Product
- Next.js
- Classifications
- CWE-942, CAPEC-63, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2026CVE publishedPublication date reported by the CVE source.
- Jan 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.0 <1.6.4
- Affected versionversion=2.0.0 <2.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo