CVE-2026-131774 in WooCommerce Fortnox Integration Plugininfo

Summary

by MITRE • 11/22/2026

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Wetail AB WooCommerce Fortnox Integration woocommerce-fortnox-integration allows Stored XSS.This issue affects WooCommerce Fortnox Integration: from n/a through 4.8.1.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/22/2026

The identified security flaw represents a classic instance of improper neutralization of input during web page generation, commonly known as Cross-Site Scripting or XSS. Specifically, this vulnerability manifests as a Stored XSS within the Wetail AB WooCommerce Fortnox Integration plugin for WordPress environments. Unlike reflected XSS attacks where malicious scripts are delivered via immediate user interaction such as clicking a crafted link, stored vulnerabilities persist on the target server. In this context, the application fails to adequately sanitize or validate untrusted input before storing it in its backend database or rendering it directly into dynamic web pages without proper encoding. This allows an attacker to inject client-side script code that is subsequently served to other users when they access the affected content, creating a persistent threat vector within the administrative interface or public-facing areas depending on where the injection point resides.

The technical root cause lies in the plugin's handling of user-supplied data related to Fortnox accounting integration settings or transactional entries. When an authenticated administrator inputs specific strings containing JavaScript payloads into fields that are later displayed without escaping, the browser interprets these scripts as legitimate code belonging to the site. This failure adheres closely to CWE-79, which defines Improper Neutralization of Input During Web Page Generation. The vulnerability affects versions from n/a through 4.8.1, indicating a long-standing issue in the software's input validation logic that has not been addressed by the vendor for an extended period. Because the data is stored server-side, every user who views the compromised page will execute the malicious script, significantly amplifying the potential impact compared to single-session attacks.

The operational impact of this vulnerability is severe due to its persistent nature and the high privilege level typically required to exploit it in e-commerce plugins. An attacker with access to an administrative account or a lower-privileged user if input fields are accessible there can steal session cookies, hijack active sessions, and perform actions on behalf of legitimate users. This includes modifying product listings, altering customer data, changing payment gateway configurations, or initiating fraudulent transactions through the Fortnox integration layer. Furthermore, because WooCommerce handles sensitive financial and personal data, a successful exploit could lead to significant regulatory compliance issues under frameworks like GDPR or PCI-DSS due to unauthorized access to protected information. The attacker can also use the compromised session to deface the website or redirect visitors to phishing sites designed to harvest credentials from customers.

From an offensive security perspective, this vulnerability maps directly to MITRE ATT&CK technique T1059.007, which covers JavaScript execution within a browser environment. It facilitates initial access and privilege escalation if lower-privileged accounts are compromised first. The persistence of the payload means that even after the original attacker's session expires, the malicious code remains active until manually removed from the database or the plugin is updated. This creates a continuous risk to the integrity and availability of the e-commerce platform.

Mitigation strategies must focus on immediate remediation through software updates and rigorous input validation practices. The primary recommendation is to upgrade the WooCommerce Fortnox Integration plugin to version 4.8.2 or later, where this vulnerability has been patched by implementing proper output encoding such as HTML entity encoding for all user-supplied data before it is rendered in the browser context. For organizations unable to update immediately due to compatibility constraints, temporary mitigations include restricting administrative access through IP whitelisting and ensuring that any custom code interacting with Fortnox endpoints performs strict server-side validation using allowlists rather than blocklists. Additionally, implementing a Content Security Policy header can help mitigate the impact by preventing unauthorized script execution even if an injection occurs. Regular security audits and penetration testing of third-party plugins are essential to identify similar flaws in other components that may share the same architectural weaknesses regarding input handling.

Responsible

Patchstack

Reservation

11/17/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!