Klarna for WooCommerce Flaw: Update Now
If your store runs Klarna for WooCommerce version 4.13.3 or older, update the plugin to the newest version today, because a flaw lets anyone on the internet read customers' order details without logging in.
This post is for owners of WooCommerce stores that take payments through Klarna, and for the agencies and freelancers who look after them. You will learn what the bug is, what data it exposes, how to check your version, how to update safely, and how to look for signs that someone already probed your store. No security background needed.
What the Klarna for WooCommerce vulnerability is
The flaw is tracked as CVE-2026-110590. A CVE is a public ID number for a known security hole, so everyone can talk about the same bug. The record was published on 2026-10-16. You can read the original entry on the NVD page for CVE-2026-110590. The NVD (National Vulnerability Database) is the US government's public catalogue of these flaws.
The NVD lists the severity as High, with a CVSS score of 7.5 out of 10. CVSS is a standard scoring system for how serious a flaw is. The NVD status is shown as "Deferred", which means the NVD has not prioritized its own detailed analysis of the record. The flaw is still published and described.
The weakness is classed as CWE-862, Missing Authorization. In plain English: the plugin does not properly check whether the person asking for some data is allowed to see it. This family of problem is called broken access control, and OWASP ranks it first among common web app risks.
Who is affected
Per the description in the record, all versions up to and including 4.13.3 of the Klarna for WooCommerce plugin are affected. That means 4.13.3 itself is not safe.
You are likely affected if:
- You run WordPress with WooCommerce and have the Klarna for WooCommerce plugin installed.
- The plugin is on version 4.13.3 or lower.
- Your store has taken orders, since the exposed data comes from real orders.
The NVD record does not list a specific fixed version. So the safe advice is simple: update to the latest version available in your WordPress dashboard, then read the plugin's changelog on its WordPress.org page. The references in the record point to a code change in the plugin's public repository, which suggests the maintainers have addressed it. Check the changelog to confirm the version you install includes the fix.
If the plugin still shows 4.13.3 or says it is up to date, and the changelog does not mention this fix, deactivate the plugin until a fixed release appears.
What data can be exposed
According to the record, an unauthenticated attacker (someone with no account and no login) can retrieve an order's secret order_key and the full billing and shipping details. That includes:
- First and last name
- Email address
- Phone number
- Street address, postcode, city, region and country
The description says this data is placed inline in a JavaScript variable called klarna_payments_params on the page. In other words, the plugin hands the data to the browser, and it does not first check that the visitor owns the order.
The score rates this mainly as a confidentiality problem (private data can be read). The record does not describe attackers changing orders, taking payments or taking the site down. But the leaked order key is itself a secret that WooCommerce uses to gate access to an order's pages, so it could give access to that order's other pages. Treat the exposed data as compromised, not merely read-only and harmless.
Why strangers could read every order
The record says WooCommerce order IDs are sequential whole numbers (1001, 1002, 1003 and so on). It also says no order key or logged-in session is needed to reach the page that holds the data. So an attacker could, in the words of the record, enumerate every order in the store with sequential GET requests to the order-pay endpoint.
Think of it like a coat check that hands over any coat if you just say a ticket number, and the tickets are numbered in a row. Nobody has to guess. They count up.
The order-pay page is the normal WooCommerce page customers use to pay for an order. It is a real page that real customers visit, which is why traffic to it looks ordinary at first glance.
How to read the score
The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N is shorthand. Here is what each part says about this bug.
| Part | Value | What it means for you |
|---|---|---|
| Attack vector | Network | Can be done over the internet |
| Attack complexity | Low | No special conditions needed |
| Privileges required | None | No account or login |
| User interaction | None | No customer has to click anything |
| Confidentiality impact | High | Private data can be read |
| Integrity impact | None | The score counts no direct changes to data (see the order key note above) |
| Availability impact | None | The site is not taken down |
The score is high because the attack is easy, needs no login and reaches personal data. It is not higher because the score counts only the reading of data, not changing it or taking the site down.
What to do right now
Most stores can fix this in about ten minutes.
- Check your version. In WordPress, go to Plugins > Installed Plugins and find Klarna for WooCommerce. The version number is under the name. If you use WP-CLI (the command line tool for WordPress), run:
wp plugin get klarna-payments-for-woocommerce --field=version
- Take a backup. Use your host's backup tool or your usual backup plugin. Updates rarely break things, but a backup means you can roll back.
- Update the plugin. In the dashboard, click Update now next to the plugin. With WP-CLI:
wp plugin update klarna-payments-for-woocommerce
- Confirm the new version. Run the version command again, or check the Plugins screen. It should be higher than 4.13.3. If the plugin still shows 4.13.3 or says it is up to date, and the changelog does not mention this fix, deactivate the plugin until a fixed release appears.
- Clear caches. Purge your caching plugin, your host's cache and any CDN (content delivery network, a service that stores copies of your pages). This makes sure visitors do not get an old copy of the page.
- Test a payment. Place a small test order with Klarna to confirm checkout still works. Use a test or low-value order and refund it if needed.
- Turn on automatic updates for payment plugins if you are comfortable with that. In Plugins > Installed Plugins, click Enable auto-updates beside the plugin.
If you cannot update today
Sometimes a custom theme or another plugin makes an instant update risky. If you must wait, the safest stopgap is to deactivate the Klarna for WooCommerce plugin until you can update. The trade-off is clear: Klarna will not be offered at checkout while it is off. For many stores a short pause is better than leaving customer data readable.
Do not rely on hiding the plugin folder name or blocking one page by hand unless a developer has tested it. Partial blocks are easy to get wrong and can break checkout.
How to check whether anyone looked
The record does not say that attacks are happening, and we have no figures on that. But after a flaw like this becomes public, it is reasonable to check your logs.
Ask your host for your web server access logs, or find them in your hosting panel. The pattern to look for is one visitor (one IP address) requesting many different order-pay pages in a short time. Normal customers only ever open their own. On a server you control, a quick look might be:
grep "order-pay" /var/log/nginx/access.log | awk '{print $1}' | sort | uniq -c | sort -rn | head
The log path depends on your host (Apache often uses /var/log/apache2/access.log). The command lists the addresses in field 1 of each log line with the most order-pay requests. If your site sits behind a CDN or proxy, field 1 may be the proxy's address. Use the real-client-IP field or your CDN's logs instead.
The command counts requests, not distinct order numbers. So when one address shows dozens or hundreds of hits, open the matching log lines and check whether the order numbers in the URLs are different each time. Many different order numbers from one visitor deserves a closer look. Bear in mind that logs may only go back a few days, and some hosts do not keep them. No suspicious entries is reassuring, but it is not proof that nothing happened.
What to tell customers
If your logs show a clear enumeration pattern, the exposed data was personal data, so you may have legal duties to notify customers or a regulator. The rules differ by country and by where your customers live. Speak to a lawyer or your data protection authority rather than guessing.
If you find nothing, you do not need to alarm anyone. In either case, it is sensible to warn your support team to be alert to customers reporting strange emails or calls that quote their order details, since names, emails and addresses are what scammers use to look convincing.
If you think your site has been broken into in other ways, such as unknown admin users or strange files, see our guide on what to do if your website was hacked.
Why bugs like this keep appearing
This is a classic access control mistake. Bugs like this are easy to miss because the page works fine for the right customer. Catching it takes someone deliberately trying to open another person's order while logged out. That is the kind of check a person has to think to make.
Plugins are also a common way in because most stores run several, each with its own code. You cannot read all of it, so the habits that help are: keep plugins updated, remove ones you do not use and buy from vendors who publish fixes quickly. Not sure how exposed your site is overall? Our guide on whether your website is hackable explains what attackers look at first, and the free website security check gives you a passive outside look at a domain you own.
Key takeaways
- Klarna for WooCommerce versions up to and including 4.13.3 are affected by CVE-2026-110590 (CVSS 7.5, High).
- Per the record, a stranger with no login can read order details, including names, emails, phone numbers, addresses and the order key. Treat that data as compromised.
- Update the plugin now, confirm the version, clear caches and test a payment. Check the plugin's changelog for the fixed release, and deactivate the plugin if no fixed release is available yet.
- Look in your access logs for one IP requesting many order-pay pages, and speak to a lawyer if you see evidence of mass access.
- Keep plugins current and remove the ones you do not use.
Where a human audit fits
Updating closes this one hole. It does not tell you whether other plugins or settings on your store have similar gaps. A Bug Circuit audit is a real person testing your website by hand, and it ends in a written report with every issue, its severity and fix steps. It is a focused small-site audit, not a compliance certificate or a multi-week enterprise pentest. If you want to see how it compares with a scanner, read manual vs automated penetration testing, then look at Bug Circuit pricing. The Essential plan is $49 one-time.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing