# CVE-2022-4948: FlyingPress <= 3.9.6 - Missing Authorization

> Authenticated subscribers can bypass authorization to modify CDN settings, potentially injecting malicious JavaScript into the site.

- **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:** 7 Jun 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-xfmg-gvv5-vrwr

## What is CVE-2022-4948?

CVE-2022-4948 is a medium-severity missing authorization vulnerability in FlyingWeb FlyingPress, published on 7 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The FlyingPress plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on its AJAX actions in versions up to, and including, 3.9.6. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to interact with the plugin in ways administrators are intended to. One action (save_config) allows for the configuration of an external CDN. This could be used to include malicious javascript from a source controlled by the attacker.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Flying-Press Flyingpress.

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

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

## Is CVE-2022-4948 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4948 is a medium-severity missing authorization vulnerability in FlyingWeb FlyingPress, published on 7 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4948 in the wild and no public exploit code.

Affected product: FlyingWeb FlyingPress. 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-4948/ (Markdown: https://insights.sbomify.com/CVE-2022-4948/index.md)
```

## Sources

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

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