LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36683: WordPress Schema Pro plugin <= 2.7.8 - Broken Access Control vulnerability

Missing Authorization vulnerability in WP SCHEMA PRO Schema Pro.This issue affects Schema Pro: from n/a through 2.7.8.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-36683 is a missing-authorization issue in the WordPress Schema Pro plugin through version 2.7.8. The main business concern is unintended exposure of confidential information. The source bundle does not identify active exploitation, a public exploit, or a confirmed fixed version.

Executive priority

Treat this as a moderate-priority WordPress exposure issue. It is not currently supported as actively exploited by the provided evidence, but the confidentiality impact is high, so internet-facing WordPress sites using Schema Pro should be checked promptly.

Technical view

The CVE describes CWE-862 missing authorization in WP SCHEMA PRO Schema Pro through 2.7.8. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges required, user interaction required, unchanged scope, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is limited to WordPress sites using Schema Pro version 2.7.8 or earlier. Sites without the plugin, or with versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed as KEV in the provided bundle. The cited sources do not state active exploitation or provide exploit availability. User interaction is required according to the CVSS vector, but the bundle does not describe the interaction or vulnerable workflow.

Researcher notes

The public bundle is sparse: it identifies product, affected range, CWE, CVSS, and Patchstack reference, but not the vulnerable endpoint, exploit path, or fixed release. Avoid assuming impact beyond confidentiality without additional vendor detail.

Mitigation direction

  • Inventory WordPress sites for Schema Pro installations and versions.
  • Prioritize any site running Schema Pro 2.7.8 or earlier.
  • Check WP Schema Pro or Patchstack guidance for recommended fixed versions or mitigations.
  • Disable the plugin where business risk is unacceptable and no confirmed fix is available.
  • Monitor WordPress logs for suspicious access to Schema Pro-related functionality.

Validation and detection

  • Confirm whether Schema Pro is installed on each WordPress site.
  • Record the installed plugin version and compare it with 2.7.8 or earlier.
  • Review vendor or Patchstack guidance for corrected-version confirmation.
  • Test authorization behavior only in approved staging or internal environments.
  • Document exposed sites, owner, remediation status, and residual risk.
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 · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2023-36683 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2023-36683Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
WP SCHEMA PROSchema Pron/aunaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.