Freemind Wp BrowserWordPress extension · Freemind Wp Browser Project
CVE-2022-2443
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe FreeMind WP Browser WordPress plugin (versions <=1.2) lacks CSRF protection (nonce validation) on its FreemindOptions() function in freemind-wp-browser.php. This allows unauthenticated attackers to trick administrators into executing malicious requests, enabling stored XSS injection via the compromised admin interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Freemind Wp BrowserWordPress extension
<= 1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify FreeMind WP Browser plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'FreeMind WP Browser' or check the plugins directory for freemind-wp-browser folderAffected if The plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin plugins list, view the plugin details to see version number, or open freemind-wp-browser.php and look for version comment/define statementAffected if Version is 1.2 or lower (or version cannot be determined but file exists)
-
Verify vulnerable function existsOpen freemind-wp-browser.php in the plugin directory and locate the FreemindOptions() functionAffected if The FreemindOptions function exists in the file
-
Check for missing nonce validationInspect the FreemindOptions() function - look for wp_verify_nonce, check_admin_referer, or nonce_field calls at the function startAffected if No nonce verification (wp_verify_nonce, check_admin_referer) is found at the beginning of the FreemindOptions() function
-
Confirm XSS-prone parameter handlingReview the function code for $_POST or $_GET parameters being output without sanitization (echo, print statements without esc_html, sanitize_text_field)Affected if User-supplied POST/GET parameters are output without proper escaping/sanitization
If the FreeMind WP Browser plugin is installed with version 1.2 or lower and the FreemindOptions() function lacks nonce verification, the environment is vulnerable to CVE-2022-2443 CSRF leading to stored XSS.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the FreeMind WP Browser plugin to version 1.3 or later, which should include proper nonce verification on the affected function. If no patch is available, disable the plugin until a secure version is released.
Fix this in Freemind Wp Browser
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2443 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data