LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1987: Scheduler Widget <= 0.1.6 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Event Modification

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1987 affects the WordPress Scheduler Widget plugin through version 0.1.6. Any logged-in user with Subscriber-level access or higher could modify scheduler events they do not own if they know the event ID. This is mainly an integrity and availability risk for sites relying on scheduled events.

Executive priority

Treat as a moderate-priority WordPress plugin issue. Prioritize sites where public registration, many subscriber accounts, or customer-facing scheduling workflows exist. It is less urgent than unauthenticated remote code execution, but it can undermine trust in published scheduling data.

Technical view

The plugin’s event update handler, identified as scheduler_widget_ajax_save_event(), lacks proper authorization and ownership checks. The issue is an IDOR/CWE-639 pattern, with related missing authorization concerns. The CVSS 3.1 score is 5.4, requiring network access and low privileges, with no user interaction.

Likely exposure

Exposure is limited to WordPress sites running Scheduler Widget up to and including 0.1.6, where untrusted or broadly assigned subscriber accounts exist. Public sources do not identify broader platform impact.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires authenticated access and knowledge of an event ID, but no user interaction is required once authenticated.

Researcher notes

Sources identify an IDOR in the event save AJAX function using an id parameter without ownership verification. No patch version is named in the provided material. Avoid assuming exploit availability beyond the documented authenticated modification condition.

Mitigation direction

  • Inventory WordPress sites for Scheduler Widget installations and versions.
  • Restrict subscriber or low-privilege account creation where not required.
  • Review vendor and WordPress plugin guidance for an updated or corrected release.
  • Disable the plugin if event integrity is business-critical and no fix is available.
  • Monitor scheduler event changes for unexpected edits by low-privilege users.

Validation and detection

  • Confirm whether Scheduler Widget is installed and at version 0.1.6 or earlier.
  • Review plugin code or vendor notes for authorization checks on event updates.
  • Check logs for event modifications by subscriber-level or unexpected accounts.
  • Verify whether business processes rely on scheduler event accuracy.
  • Track the CVE and vendor pages for remediation updates.
Prepared
Confidence
high
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1987 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-1987Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
morelmathieujScheduler Widget0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.