# CVE-2023-47689: WordPress Animator plugin <= 3.0.10 - Unauthenticated Plugin Settings Change Vulnerability

> Unauthenticated attackers can modify plugin settings due to missing authorization checks in the Animator WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-2p7v-6q2g-9wg5

## What is CVE-2023-47689?

CVE-2023-47689 is a medium-severity missing authorization vulnerability in Toast Plugins Animator, published on 2 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in Toast Plugins Animator allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Animator: from n/a through 3.0.10.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-47689?


## How do I fix CVE-2023-47689?

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

## Is CVE-2023-47689 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47689 and fix it if it is affected.

What it is: CVE-2023-47689 is a medium-severity missing authorization vulnerability in Toast Plugins Animator, published on 2 Jan 2025. 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-2023-47689 in the wild and no public exploit code.

Affected product: Toast Plugins Animator. 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-2023-47689/ (Markdown: https://insights.sbomify.com/CVE-2023-47689/index.md)
```

## Sources

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

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