dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-11191

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-31
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 RealPress WordPress plugin before 1.1.0 registers the REST routes without proper permission checks, allowing the creation of pages and sending of emails from the site.

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 RealPress WordPress plugin before version 1.1.0 registers REST API routes without implementing proper permission_callback functions, allowing unauthenticated or low-privilege users to create arbitrary pages and send emails through the site via the exposed REST endpoints.

MitigationUpdate the RealPress plugin to version 1.1.0 or later which includes proper permission checks on REST route registrations. If immediate update is not possible, consider disabling the plugin or restricting REST API access at the server level.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify RealPress plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'realpress' or list installed plugins via WP-CLI: wp plugin list --name=realpress
    Affected if The RealPress plugin folder exists and the plugin is active in WordPress
  2. Identify installed RealPress version
    Read the main plugin file (realpress.php) header or use WP-CLI: wp plugin get realpress --field=version
    Affected if The installed version is lower than 1.1.0 (e.g., 1.0.9, 1.0.8, etc.)
  3. Confirm REST API endpoints are exposed
    Query the WordPress REST API for RealPress routes: GET /wp-json/wp/v2/routes or /wp-json/realpress/v1/ and examine the response for registered endpoints
    Affected if REST endpoints under the RealPress namespace (e.g., /wp-json/realpress/v1/) return a response without requiring authentication
  4. Verify permission_callback absence on vulnerable endpoints
    Inspect the plugin source code in wp-content/plugins/realpress/ for REST route registration (usually in includes/class-realpress-rest-api.php or the main plugin file) and check if 'permission_callback' is defined for each endpoint
    Affected if The registered REST routes lack a 'permission_callback' argument or the callback returns true/empty for unauthenticated users (e.g., '__return_true' or no callback defined)
  5. Test unauthenticated access to sensitive endpoints
    Send a POST request to the RealPress REST endpoints (e.g., to create a page or send an email) without providing authentication credentials using curl or a similar tool
    Affected if The request succeeds without returning a 401 or 403 error, indicating the endpoint is accessible to unauthenticated users

A user is affected if the RealPress plugin version is below 1.1.0 AND the REST API endpoints are exposed without proper permission_callback functions, allowing unauthenticated page creation or email sending.

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 RealPress plugin to version 1.1.0 or later which includes proper permission checks on REST route registrations. If immediate update is not possible, consider disabling the plugin or restricting REST API access at the server level.

Recommended fix Moderate confidence

RealPress plugin version 1.1.0

  1. 1. Back up your WordPress site (database and files) before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find the RealPress plugin in the installed plugins list
  4. 4. If an update is available, click 'Update Now' to update to version 1.1.0 or later
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload version 1.1.0 if auto-update is not available
  6. 6. After updating, verify the plugin version shows 1.1.0 or higher
  7. 7. Test that the REST API endpoints now require proper authentication (the authorization vulnerability should be remediated)
Caveat Review plugin settings after upgrade as any configuration changes between versions should be verified

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11191 — 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-11191 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