dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13528

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-05
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 Feedback Modal for Website plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'handle_export' function in all versions up to, and including, 1.0.1. This makes it possible for unauthenticated attackers to export all feedback data in CSV or JSON format via the 'export_data' parameter.

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

This is a Broken Access Control vulnerability in the WordPress Feedback Modal plugin. The 'handle_export' function lacks a capability check, allowing unauthenticated attackers to export all feedback data in CSV or JSON format by manipulating the 'export_data' parameter. The flaw enables complete exposure of sensitive user feedback without any authentication.

MitigationUpdate the plugin to version 1.0.2 or later which includes the missing capability check. If no update is available, add a WordPress capability check (e.g., current_user_can('manage_options')) to the handle_export function before processing the export request.

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. Confirm WordPress Feedback Modal plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Feedback Modal' in the installed plugins list, or search the wp-content/plugins directory for a folder named 'feedback-modal' or similar
    Affected if The plugin is installed and active on the WordPress site
  2. Identify the installed plugin version
    In the WordPress admin, go to Plugins > Installed Plugins > Feedback Modal and note the version number displayed, or read the main plugin PHP file header which contains the 'Version' tag
    Affected if The version is 1.0.1 or earlier (versions prior to the 1.0.2 patch)
  3. Locate the handle_export function in plugin code
    Using a file manager or FTP, navigate to the plugin directory and open the PHP file containing the handle_export function; this is typically in the main plugin file or an admin/class file
    Affected if The function exists and processes the export_data parameter without a current_user_can() capability check before executing
  4. Verify export functionality is accessible without authentication
    Test the export endpoint (commonly wp-admin/admin-ajax.php?action=feedback_modal_export or similar, check plugin for exact action name) using a tool like curl or browser dev tools while NOT logged in, sending a request with the export_data parameter
    Affected if The export returns CSV or JSON data containing feedback without requiring any authentication token or login session

A user is affected if the WordPress Feedback Modal plugin versions 1.0.1 or earlier are installed and the export functionality can be accessed without authentication, exposing sensitive feedback data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.0.2 or later which includes the missing capability check. If no update is available, add a WordPress capability check (e.g., current_user_can('manage_options')) to the handle_export function before processing the export request.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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