CVE-2025-11881

AppPresser – Mobile App Framework <= 4.5.0 - Missing Authorization to Unauthenticated Limited Sensitive Information Exposure

2025-10-29 00:00
D01EXPLOIT OFFICIAL

Strategic Overview

Status
Patched in 4.5.1
Affected Version
<= 4.5.0
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-11881
View all AppPresser – Mobile App Framework vulnerabilities

At a glance

CVE-2025-11881 is a medium-severity Missing Authorization vulnerability in the AppPresser WordPress plugin, affecting versions <= 4.5.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.5.1; sites on affected versions should update now. Disclosed October 2025, reported by D01EXPLOIT OFFICIAL.

Vulnerability Overview

The AppPresser – Mobile App Framework plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'myappp_verify' function in all versions up to, and including, 4.5.0. This makes it possible for unauthenticated attackers to extract sensitive data including plugin and theme names and version numbers, which can be used to facilitate targeted attacks against outdated or vulnerable components.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

AppPresser <= 4.5.0 carries this weakness at myappp_verify, and reaching it takes no account at all. 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 AppPresser the fix is 4.5.1: builds <= 4.5.0 are affected, anything from 4.5.1 onward is not.

Remediation

Update to version 4.5.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: AppPresser 4.5.1 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