CVE-2022-45803 is a medium severity (CVSS 6.5) missing authorization flaw in the WordPress Form Builder Plugin Gutenberg Forms, versions through 2.2.8.3. A logged in user with low privileges can do something they should not be allowed to. Update to version 2.2.9 or later.
What's affected
The record lists WordPress Form Builder Plugin, Gutenberg Forms, from the earliest release through 2.2.8.3. Patchstack's entry says the vulnerable versions are 2.2.8.3 and below, and that the fix landed in 2.2.9. Patchstack lists the required privilege as Subscriber, which is the lowest logged in role.
The NVD entry was published on 21 June 2024, while Patchstack published its entry on 6 February 2023. The fix is older than the CVE record.
How to check if you're exposed
In the WordPress admin, open Plugins and read the version shown under Form Builder Plugin, Gutenberg Forms. With WP-CLI you can run wp plugin list --fields=name,status,version and look for the entry. Check inactive plugins too, since a deactivated plugin still sits on disk.
What to do now
- Update the plugin to 2.2.9 or later from the Plugins screen, then confirm the version number afterwards.
- If an update is not available yet, deactivate and delete the plugin, or restrict access to it while you wait. Do not leave a vulnerable copy installed but switched off.
- Review your site for changes you did not make, such as new accounts, altered content or unexpected files, and rotate credentials if anything looks wrong.
- Add the plugin to your inventory so the next advisory for it reaches you without a manual search.
Why it matters
The class is CWE-862, missing authorization. The plugin exposes an action that checks whether a user is logged in, but not whether that user is allowed to perform it. On a site that lets visitors register, anyone can obtain a Subscriber account and reach the action.
The record scores integrity impact as high and nothing else, which fits an action that changes data. KEV status is false. Sites that do not allow public registration are less exposed, but still should update.
A practical note for WordPress owners: plugin flaws that need only a Subscriber account are easy to overlook, because the account looks harmless. If your site allows open registration, review the list of users, remove accounts you do not recognize, and consider setting the default role for new users to the lowest available one.
Quick check
Who can exploit CVE-2022-45803?
Per Patchstack, a user with at least the Subscriber role. Sites with open registration make that easy to obtain.
Which version fixes it?
Patchstack lists 2.2.9 as the patched version.
Sources
You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.
Last reviewed: 19 October 2026.