Skip to main content
Menu
CVEs

Wetail WooCommerce Fortnox Integration broken access control in accounting integration

CVE-2026-131773Published , updated

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.8.2
Who is exposed
Not reported

Summary

The Wetail AB WooCommerce Fortnox Integration plugin for WordPress has a missing authorization flaw that lets an attacker reach functions they should not have access to. It can be reached remotely over the network without logging in.

Written by a model

Original description

Missing Authorization vulnerability in Wetail AB WooCommerce Fortnox Integration woocommerce-fortnox-integration allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WooCommerce Fortnox Integration: from n/a through 4.8.1.

Who should check

Teams running the WooCommerce Fortnox Integration WordPress plugin version 4.8.1 or earlier, such as WordPress and WooCommerce store operators

“<= 4.8.1 Vulnerable version(s)”

patchstack.com

What to do

Upgrade to a fixed version: 4.8.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131773 (WordPress WooCommerce Fortnox Integration plugin <= 4.8.1 - Broken Access Control vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131773 (entry last updated 2026-11-22):
Affected:
- Wetail AB WooCommerce Fortnox Integration: fixed in 4.8.2
Fixed versions: 4.8.2.
Conditions (all must be true for the bug to be hit):
- WooCommerce Fortnox Integration plugin version 4.8.1 or earlier (source: https://patchstack.com/database/wordpress/plugin/woocommerce-fortnox-integration/vulnerability/wordpress-woocommerce-fortnox-integration-plugin-4-8-1-broken-access-control-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-131773 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131773 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/woocommerce-fortnox-integration/vulnerability/wordpress-woocommerce-fortnox-integration-plugin-4-8-1-broken-access-control-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-131773
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131773
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131773"}.

Affected versions

cve.now Index

24Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

Questions about CVE-2026-131773

Is CVE-2026-131773 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The plugin fails to properly restrict access in some places, so users can reach pages or perform actions they should not be allowed to. The advisory gives viewing other people's data as an example.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-131773?

woocommerce-fortnox-integration: through 4.8.1 (fixed in 4.8.2).

Source: cve.now feed data

Am I affected, and how do I check?

WooCommerce Fortnox Integration plugin by Wetail AB, version 4.8.1 and earlier. Check the installed plugin version in the WordPress Plugins screen or the plugin's header information.

Source: patchstack.com, cve.org

How do I fix CVE-2026-131773?

Update the WooCommerce Fortnox Integration plugin to version 4.8.2 or later.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.