CVE-2025-31878

UPC/EAN/GTIN Code Generator <= 2.0.2 - Missing Authorization to Authenticated (Subscriber+) Settings Update

2025-04-01 00:00
Kévin Mosbahi (Mika)

Strategic Overview

Status
Patched in 2.0.3
Affected Version
<= 2.0.2
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-31878
View all UPC/EAN/GTIN Barcode Generator/Importer vulnerabilities

At a glance

CVE-2025-31878 is a medium-severity Missing Authorization vulnerability in the UPC/EAN/GTIN Barcode Generator/Importer WordPress plugin, affecting versions <= 2.0.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.3; sites on affected versions should update now. Disclosed April 2025, reported by Kévin Mosbahi (Mika).

Vulnerability Overview

The UPC/EAN/GTIN Code Generator plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 2.0.2. This makes it possible for authenticated attackers, with subscriber-level access and above, to update plugin settings.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in UPC/EAN/GTIN Barcode Generator/Importer <= 2.0.2 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For UPC/EAN/GTIN Barcode Generator/Importer the fix is 2.0.3: builds <= 2.0.2 are affected, anything from 2.0.3 onward is not.

Remediation

Update to version 2.0.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: UPC/EAN/GTIN Barcode Generator/Importer 2.0.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C