# CVE-2022-1203: Content Mask < 1.8.4.1 - Subscriber+ Arbitrary Options Update

> Authenticated subscribers can modify arbitrary blog options due to missing authorization and CSRF checks in the Content Mask WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 May 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-q5pj-mjjc-c94j

## What is CVE-2022-1203?

CVE-2022-1203 is a medium-severity missing authorization vulnerability in Unknown Content Mask, published on 30 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Content Mask WordPress plugin before 1.8.4.1 does not have authorisation and CSRF checks in various AJAX actions, as well as does not validate the option to be updated to ensure it belongs to the plugin. As a result, any authenticated user, such as subscriber could modify arbitrary blog options

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-1203?

It affects 1 product.


Products: Content Mask Project Content Mask.

## How do I fix CVE-2022-1203?

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

## Is CVE-2022-1203 being exploited?

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

Public exploit code:

- Content Mask < 1.8.4 - Subscriber+ Arbitrary Options Update (github_poc): https://github.com/RandomRobbieBF/CVE-2022-1203

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1203 and fix it if it is affected.

What it is: CVE-2022-1203 is a medium-severity missing authorization vulnerability in Unknown Content Mask, published on 30 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1203 in the wild and no public exploit code.

Affected product: Unknown Content Mask. 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-2022-1203/ (Markdown: https://insights.sbomify.com/CVE-2022-1203/index.md)
```

## Sources

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

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