# CVE-2026-2504: Dealia – Request a quote <= 1.0.7 - Missing Authorization to Authenticated (Contributor+) Plugin Configuration Reset

> Authenticated contributors can reset plugin configuration due to missing capability checks in AJAX handlers.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-f4vx-r87q-vg6c

## What is CVE-2026-2504?

CVE-2026-2504 is a medium-severity missing authorization vulnerability in Dealia – Request a quote, published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Dealia – Request a quote plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on multiple AJAX handlers in all versions up to, and including, 1.0.7. The admin nonce (DEALIA_ADMIN_NONCE) is exposed to all users with edit_posts capability (Contributor+) via wp_localize_script() in PostsController.php, while the AJAX handlers in AdminSettingsController.php only verify the nonce without checking current_user_can('manage_options'). This makes it possible for authenticated attackers, with Contributor-level access and above, to reset the plugin configuration.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-2504 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2504 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2504 is a medium-severity missing authorization vulnerability in Dealia – Request a quote, published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2504 in the wild and no public exploit code.

Affected product: Dealia – Request a quote. 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-2504/ (Markdown: https://insights.sbomify.com/CVE-2026-2504/index.md)
```

## Sources

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

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