dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-15507

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-04
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 Magic Import Document Extractor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the ajax_sync_usage() function in all versions up to, and including, 1.0.5. This makes it possible for unauthenticated attackers to modify the plugin's license status and credit balance.

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 Magic Import Document Extractor WordPress plugin has a Broken Access Control vulnerability where the ajax_sync_usage() function lacks a capability check. This allows unauthenticated attackers to make AJAX calls that modify the plugin's license status and credit balance, as no authorization is enforced on this sensitive function.

MitigationUpdate the plugin to version 1.0.6 or later, which should include proper capability checks on the ajax_sync_usage() function. Until then, consider disabling the plugin or restricting AJAX access at the web 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 Magic Import Document Extractor plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Magic Import Document Extractor' in the installed plugins list, or inspect the file /wp-content/plugins/ directory for a folder containing 'magic-import' or similar naming
    Affected if The plugin is present in the plugins directory
  2. Determine the installed plugin version
    In WordPress admin > Plugins, find the plugin and view the version number under the plugin name, or read the main plugin PHP file header for the 'Version' tag
    Affected if Version is below 1.0.6 (the vulnerable version range)
  3. Confirm AJAX endpoint is accessible
    Make a test request to your site's /wp-admin/admin-ajax.php endpoint - this is exposed if the site responds to unauthenticated requests
    Affected if The AJAX endpoint responds without requiring authentication
  4. Identify if ajax_sync_usage function exists in the plugin
    Search the plugin files (typically in wp-content/plugins/[plugin-folder]/includes/ or the main plugin file) for the string 'ajax_sync_usage' using a file search or grep tool
    Affected if The function is present in the plugin code and no capability check is found in its definition

The environment is affected if the Magic Import Document Extractor plugin is installed with a version lower than 1.0.6 and the ajax_sync_usage function is accessible via the site's AJAX endpoint.

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 1.0.6 or later, which should include proper capability checks on the ajax_sync_usage() function. Until then, consider disabling the plugin or restricting AJAX access at the web server level.

Recommended fix Moderate confidence

Version 1.0.6 or latest available version (upgrade from 1.0.5 and below)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Magic Import Document Extractor' plugin
  4. Check if an update is available and update to the latest version
  5. If no update is visible in WordPress, manually download the latest version from the WordPress plugin repository and reinstall

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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