# CVE-2026-3527: AJAX Dashboard - Critical - Access bypass - SA-CONTRIB-2026-022

> Attackers can bypass authentication to access critical functions in the Drupal AJAX Dashboard module.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** DRUPAL-CONTRIB-2026-022, GHSA-c3p6-9m4j-2c45

## What is CVE-2026-3527?

CVE-2026-3527 is a medium-severity missing authorization vulnerability in Drupal AJAX Dashboard, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authentication for Critical Function vulnerability in Drupal AJAX Dashboard allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects AJAX Dashboard: from 0.0.0 before 3.1.0.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


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

Products: Ceriumsoft Ajax Dashboard.

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

Upgrade to a fixed version.

## Is CVE-2026-3527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3527 is a medium-severity missing authorization vulnerability in Drupal AJAX Dashboard, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3527 in the wild and no public exploit code.

Affected product: Drupal AJAX Dashboard. 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-3527/ (Markdown: https://insights.sbomify.com/CVE-2026-3527/index.md)
```

## Sources

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

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