CVE-2025-10303

Library Management System <= 3.1 - Missing Authorization to Authenticated (Subscriber+) Settings Manipulation

2025-10-14 19:59
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 3.2
Affected Plugin
Library Management System
Affected Version
<= 3.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-10303
View all Library Management System vulnerabilities

At a glance

CVE-2025-10303 is a medium-severity Missing Authorization vulnerability in the Library Management System WordPress plugin, affecting versions <= 3.1. 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 3.2; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.

Vulnerability Overview

The Library Management System plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the owt7_library_management_ajax_handler() function in all versions up to, and including, 3.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update and manipulate several of the plugin's settings and features.

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

Library Management System <= 3.1 carries this weakness at owt7_library_management_ajax_handler(), and reaching it 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 Library Management System the fix is 3.2: builds <= 3.1 are affected, anything from 3.2 onward is not.

Remediation

Update to version 3.2, 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: Library Management System 3.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-10303https://www.wordfence.com/threat-intel/vulnerabilities/id/9e45feb6-5ffa-4ad3-9549-4414988f040ehttps://nvd.nist.gov/vuln/detail/CVE-2025-10303

Related records

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