dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-1987

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Scheduler Widget plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 0.1.6. This is due to the `scheduler_widget_ajax_save_event()` function lacking proper authorization checks and ownership verification when updating events. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify any event in the scheduler via the `id` parameter granted they have knowledge of the event ID.

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 Scheduler Widget WordPress plugin has an IDOR vulnerability in the scheduler_widget_ajax_save_event() function. Authenticated users with Subscriber-level access can modify any event by manipulating the event ID parameter due to missing authorization checks and ownership verification.

MitigationImplement proper authorization checks in scheduler_widget_ajax_save_event() to verify event ownership before allowing modifications, or update to the latest plugin version when available.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 Scheduler Widget plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find Scheduler Widget. Note the installed version number. Alternatively, check the plugin header in wp-content/plugins/scheduler-widget/scheduler-widget.php for the Version field.
    Affected if The plugin is installed and the installed version lacks the authorization fix (compare to latest version if known)
  2. Locate the vulnerable function in plugin files
    Access the WordPress site files via FTP or file manager. Navigate to wp-content/plugins/scheduler-widget/ and search for the function scheduler_widget_ajax_save_event() in PHP files.
    Affected if The function exists in the codebase, indicating the potentially vulnerable code is present
  3. Verify Subscriber role has access to the AJAX action
    In the plugin files, locate where wp_ajax_ or wp_ajax_nopriv_ hooks are defined. Check if scheduler_widget_ajax_save_event is hooked to an action accessible to subscriber-level users (typically roles with 'edit_posts' capability or lower).
    Affected if Subscriber or lower-privileged user roles can trigger the AJAX action without elevated permissions
  4. Inspect the function for missing authorization checks
    Open the file containing scheduler_widget_ajax_save_event(). Examine the function code to see if it verifies the current user owns the event before allowing modifications. Look for checks like get_post_field('post_author', $event_id) === get_current_user_id() or similar ownership validation.
    Affected if The function lacks code that verifies the logged-in user owns the event before saving changes
  5. Test event ID manipulation capability
    As a user with Subscriber role, attempt to modify an event created by a different user by intercepting the AJAX request and changing the event ID parameter to a value belonging to another user.
    Affected if The modification succeeds without ownership verification, confirming the IDOR vulnerability

If Subscriber-level users can modify events they did not create by manipulating the event ID parameter, the environment is affected by this IDOR vulnerability.

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

Implement proper authorization checks in scheduler_widget_ajax_save_event() to verify event ownership before allowing modifications, or update to the latest plugin version when available.

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-2026-1987 — 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-2026-1987 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