CVE-2022-2443: The FreeMind WP Browser plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, an

Q: How do I fix CVE-2022-2443?

freemind wp browser: upgrade to newer than 1.2. Exact commands for each OS are on this page.

Q: Is CVE-2022-2443 being exploited?

CVE-2022-2443 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-2443 affect?

CVE-2022-2443 affects freemind wp browser. Severity is high (CVSS 8.8). The FreeMind WP Browser plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including 1.2. This is due to missing nonce protection on the FreemindOptions() function found in the ~/freemind-wp-browser.php

This month

HIGH 8.8UPGRADE

CVE-2022-2443 is a high-severity flaw (CVSS 8.8) affecting freemind wp browser. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The FreeMind WP Browser plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including 1.2. This is due to missing nonce protection on the FreemindOptions() function found in the ~/freemind-wp-browser.php file. This makes it possible for unauthenticated attackers to inject malicious web scripts into the page, granted they can trick a site's administrator into performing an action such as clicking on a link.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-07-18
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: freemind wp browser project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-07-18 17:15 UTCPublished CVE record published
2026-06-17 04:41 UTCUpdated Record last modified

freemind wp browser project freemind wp browser UPGRADE

Affected: <= 1.2

Fixed in: newer than 1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy freemind-wp-browser || rpm -q freemind-wp-browser || freemind-wp-browser --version

2. UPGRADE to newer than 1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade freemind-wp-browser

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade freemind-wp-browser

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2443?

freemind wp browser: upgrade to newer than 1.2. Exact commands for each OS are on this page.

Is CVE-2022-2443 being exploited?

CVE-2022-2443 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2443 affect?

CVE-2022-2443 affects freemind wp browser. Severity is high (CVSS 8.8). The FreeMind WP Browser plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including 1.2. This is due to missing nonce protection on the FreemindOptions() function found in the ~/freemind-wp-browser.php

How urgent is CVE-2022-2443?

Priority 43/100. High severity

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs