# CVE-2024-1994: Image Watermark <= 1.7.3 - Missing Authorization to Authenticated (Subscriber+) Watermark Modification

> Authenticated subscribers can modify image watermarks due to missing capability checks in the Image Watermark WordPress plugin.

- **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:** 6 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-h896-g8fr-jxm5

## What is CVE-2024-1994?

CVE-2024-1994 is a medium-severity missing authorization vulnerability in dfactory Image Watermark, published on 6 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Image Watermark plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the watermark_action_ajax() function in all versions up to, and including, 1.7.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to apply and remove watermarks from images.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-1994?


## How do I fix CVE-2024-1994?

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

## Is CVE-2024-1994 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1994 and fix it if it is affected.

What it is: CVE-2024-1994 is a medium-severity missing authorization vulnerability in dfactory Image Watermark, published on 6 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1994 in the wild and no public exploit code.

Affected product: dfactory Image Watermark. 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-2024-1994/ (Markdown: https://insights.sbomify.com/CVE-2024-1994/index.md)
```

## Sources

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

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