# CVE-2026-1833: Missing authorization in WaMate Confirm – Order Confirmation

> Authenticated subscribers can arbitrarily block or unblock phone numbers due to missing authorization checks in the WaMate Confirm plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** No
- **Published:** 11 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-prgq-3hfx-hfpx

## What is CVE-2026-1833?

CVE-2026-1833 is a medium-severity missing authorization vulnerability in sm_rasmy WaMate Confirm – Order Confirmation, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WaMate Confirm – Order Confirmation plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 2.0.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to block and unblock phone numbers, which should be restricted to administrators.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-1833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1833 is a medium-severity missing authorization vulnerability in sm_rasmy WaMate Confirm – Order Confirmation, published on 11 Feb 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-1833 in the wild and no public exploit code.

Affected product: sm_rasmy WaMate Confirm – Order Confirmation. 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-1833/ (Markdown: https://insights.sbomify.com/CVE-2026-1833/index.md)
```

## Sources

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

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