dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-11881

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The AppPresser WordPress plugin has a broken access control vulnerability in the 'myappp_verify' function, which lacks a capability check and is accessible to unauthenticated users. Attackers can call this function to enumerate installed plugins and themes along with their version numbers, providing valuable reconnaissance data for targeted attacks.

MitigationUpdate the plugin to version 4.5.1 or later if available; otherwise, add a capability check (e.g., current_user_can('manage_options')) and nonce verification to the 'myappp_verify' function to restrict access to authorized users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if AppPresser plugin is installed
    Navigate to WP Admin > Plugins and look for 'AppPresser' in the installed plugins list, or inspect the file /wp-content/plugins/apppresser/ for the plugin directory
    Affected if AppPresser plugin is present in the WordPress installation
  2. Identify installed AppPresser version
    In WP Admin > Plugins, click on AppPresser to view the version number, or check the plugin main file header in /wp-content/plugins/apppresser/ for the 'Version' field
    Affected if The version is lower than 4.5.1 or cannot be determined (indicating an unpatched version)
  3. Locate the vulnerable myappp_verify function
    Search the plugin files in /wp-content/plugins/apppresser/ for the string 'function myappp_verify' or 'myappp_verify' to confirm the function exists
    Affected if The function 'myappp_verify' is found in the plugin code
  4. Test unauthenticated access to the vulnerable endpoint
    Send a GET or POST request to the WordPress AJAX endpoint (usually /wp-admin/admin-ajax.php?action=myappp_verify) or the REST API route if used, without providing any authentication cookies or credentials
    Affected if The request returns a response containing plugin/theme enumeration data without requiring login (HTTP 200 without authentication)

A user is affected if AppPresser version is below 4.5.1 (or unverified) AND the myappp_verify function responds to unauthenticated requests with sensitive plugin/theme version information.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 4.5.1 or later if available; otherwise, add a capability check (e.g., current_user_can('manage_options')) and nonce verification to the 'myappp_verify' function to restrict access to authorized users only.

Recommended fix High confidence

4.5.1 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'AppPresser – Mobile App Framework' plugin
  4. 4. Check the current installed version is 4.5.0 or below
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version (4.5.1 or higher)
  6. 6. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. 7. Verify the update completed successfully and the plugin is now running version 4.5.1 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11881 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data