LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24950: WordPress Authorsy plugin <= 1.0.6 - Insecure Direct Object References (IDOR) vulnerability

Authorization Bypass Through User-Controlled Key vulnerability in themeplugs Authorsy authorsy allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Authorsy: from n/a through <= 1.0.6.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24950 affects the WordPress Authorsy plugin through version 1.0.6. It is an authorization bypass issue where attackers may access information they should not be allowed to view. The published scoring rates confidentiality impact as high. Public sources do not show CISA KEV listing or confirmed active exploitation.

Executive priority

Treat this as a high-priority WordPress plugin exposure. Prioritize internet-facing sites using Authorsy, especially where author or user-related information is sensitive. If no vendor fix is available, reduce risk by removing the plugin where feasible and monitoring closely.

Technical view

The issue is an Insecure Direct Object Reference/authorization bypass in themeplugs Authorsy, mapped to CWE-639. CVSS 3.1 is 7.5 with network access, low complexity, no privileges, and no user interaction required. The vector indicates high confidentiality impact, with no integrity or availability impact stated.

Likely exposure

Exposure is likely limited to WordPress sites running the Authorsy plugin at version 1.0.6 or earlier. The source bundle does not identify other affected products, hosting platforms, or a fixed version.

Exploitation context

Public sources describe the vulnerability class and impact but do not provide evidence of active exploitation. The CVE is not marked as CISA KEV in the provided data. Attack feasibility appears meaningful because the CVSS vector requires no privileges or user interaction.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. The record states affected Authorsy versions through 1.0.6 and CVSS 7.5. No exploit details, fixed version, or active exploitation confirmation are present in the provided sources.

Mitigation direction

  • Inventory WordPress sites for the Authorsy plugin and version.
  • If Authorsy is not required, disable or remove it.
  • If installed at version 1.0.6 or earlier, check vendor and Patchstack guidance.
  • Apply a vendor-provided fixed release if one is published.
  • Increase monitoring for unusual access to author-related data.

Validation and detection

  • Confirm whether Authorsy is installed on each WordPress site.
  • Record the installed Authorsy version and compare against <= 1.0.6.
  • Review CVE and Patchstack entries for updated remediation guidance.
  • Check access logs for unusual unauthenticated requests to Authorsy-related resources.
  • Document compensating controls if the plugin cannot be removed.
Prepared
Confidence
medium
Sources
3

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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24950 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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
2Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-24950Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
themeplugsAuthorsyauthorsy, 0unaffected
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.