CERT-In’s Critical Warning About Nine Drupal Modules
CERT-In is India’s Computer Emergency Response Team, and it works under the Ministry of Electronics and Information Technology. On 6 November 2026, it issued vulnerability note CIVN-2026-0541. It rates the risk as Critical, and it covers nine contributed modules for Drupal.
Drupal is a free, open-source system that people use to build and manage websites. Contributed modules are add-ons that give a site extra features. One flaw in an old add-on can put the whole site at risk. So it helps a lot to keep a list of the modules your site uses.
Which modules are affected
- Simple OAuth (OAuth2) & OpenID Connect: before 5.2.6, from 6.0.0 to 6.0.9, and from 6.1.1 to 6.1.3
- REST & JSON API Authentication for Drupal: before 3.2.1
- Reset Password Email/SMS OTP: before 1.0.5
- S3 File System CORS Upload: before 8.x-1.3
- Content Synchronizer: before 4.1.1
- Workflow Notifications: before 3.0.3
- Commerce Product Alternative: before 1.0.1
- Highlight Js syntax highlighter: before 1.3.1
- GroupEx PRO (Daxko) integration: before 2.2.1
What attackers could do
CERT-In says the problems come from weak access controls, wrong login checks, poor checking of user input and unsafe PHP object deserialization. The last one means a site rebuilds program objects from data that an attacker might control.
An attacker could send specially made requests, change the inputs a site accepts, or take advantage of badly set access controls. CERT-In says this could let them skip login and permission checks, reach or change protected data, run cross-site scripting (XSS) attacks, or run any code they want. The note lists unauthorised access, data leaks, harmful scripts and account takeover as risks. It says a site could be completely compromised.
What administrators should do
CERT-In’s fix is to upgrade each module to the latest version listed in the Drupal security advisories. The note links to nine of these advisories for the exact fixed versions.
First, check which of the nine modules your site has. Then take a backup, test the updates on a copy of the site, and update the live site. If you don’t need a module, you can just remove it. This routine is my own suggestion, not from CERT-In.
My thoughts
This part is my own opinion. Drupal’s advisories for at least three of these modules, including the OTP password reset one, are dated 4 November. That is two days before CERT-In’s note. So teams that follow Drupal’s own security feed might have had a head start.
The note doesn’t say attackers are already using these flaws. So I read it as an early warning, not a report of a break-in. Many of these modules handle logins, password resets and API access. After updating, test those parts. A broken reset or sign-in can lock real users out, but a missed update leaves a door open for attackers.