LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51362: WordPress myStickyElements plugin <= 2.1.3 - Broken Access Control vulnerability

Missing Authorization vulnerability in Premio My Sticky Elements mystickyelements allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects My Sticky Elements: from n/a through <= 2.1.3.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites using Premio My Sticky Elements up to 2.1.3. A missing authorization check could let an unauthenticated remote actor make limited unauthorized changes. The published score is medium, with low integrity impact and no stated confidentiality or availability impact. The source bundle does not name a fixed version or active exploitation.

Executive priority

Treat this as a moderate WordPress plugin risk. It is not presented as actively exploited, but unauthenticated remote reachability makes affected public sites worth prompt inventory and remediation through vendor guidance.

Technical view

CVE-2023-51362 is CWE-862 missing authorization in the mystickyelements WordPress plugin. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact only. The available sources identify affected versions through 2.1.3 but do not provide exploit details or remediation specifics.

Likely exposure

Exposure is likely limited to WordPress installations with the Premio My Sticky Elements plugin installed at version 2.1.3 or earlier. Sites not using this plugin are not indicated as affected by the provided sources.

Exploitation context

The bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates remote unauthenticated reachability without user interaction, but the documented impact is limited to integrity and rated medium.

Researcher notes

The affected product is Premio My Sticky Elements, package name mystickyelements. The CVE description says versions through 2.1.3 are affected. Evidence is incomplete on exact vulnerable functionality, fixed version, and exploit availability, so validation should avoid assumptions beyond installed product and version exposure.

Mitigation direction

  • Inventory WordPress sites for the mystickyelements plugin and version.
  • Check Premio and Patchstack guidance for a fixed release or vendor workaround.
  • Update the plugin if a vendor-fixed version is available.
  • Disable or remove the plugin where business impact is acceptable.
  • Prioritize internet-facing WordPress sites using affected versions.

Validation and detection

  • Confirm whether My Sticky Elements is installed on each WordPress site.
  • Record plugin versions and flag 2.1.3 or earlier as affected.
  • Review WordPress change history for unexpected plugin configuration changes.
  • Verify remediation by confirming the plugin is removed, disabled, or vendor-fixed.
  • Track CVE and Patchstack updates for remediation details.
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-51362 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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
PremioMy Sticky Elementsmystickyelements, 0unaffected
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.