LiveActive security incident?Get immediate response
CVE Record

CVE-2023-27450: WordPress Leyka Plugin <= 3.29.2 is vulnerable to Cross Site Scripting (XSS)

Unauth. Stored Cross-Site Scripting (XSS) vulnerability in Teplitsa of social technologies Leyka plugin <= 3.29.2 versions.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A vulnerable Leyka WordPress donation plugin version can store malicious script content that later runs in another user's browser. That could expose data, alter page behavior, or damage trust when a staff member or visitor views affected content. The supplied record rates this high, but does not confirm active exploitation.

Executive priority

Prioritize remediation for public WordPress sites using Leyka, especially donation workflows. This is high severity because unauthenticated stored XSS can affect users after content is saved, but the supplied evidence does not show confirmed active exploitation.

Technical view

CVE-2023-27450 is an unauthenticated stored XSS issue in Teplitsa of social technologies Leyka for WordPress, described for versions <= 3.29.2. It is mapped to CWE-79 with CVSS 3.1 score 7.1, network attack vector, low complexity, no privileges required, and user interaction required.

Likely exposure

Exposure is likely limited to WordPress sites with the Leyka plugin installed at version 3.29.2 or earlier. The bundle does not provide CPEs or a fixed-version statement, so confirm against local plugin inventory and vendor guidance.

Exploitation context

The source bundle describes unauthenticated stored XSS requiring user interaction. The KEV flag is false, and no provided source reports active exploitation. Treat internet-facing donation or campaign pages as higher priority because they may process public input.

Researcher notes

The record lacks detailed affected-version metadata, CPEs, fixed-version data, and exploit-status confirmation beyond the false KEV flag. Validation should focus on installed Leyka versions, public input paths, and evidence of stored script content without attempting weaponized reproduction.

Mitigation direction

  • Inventory WordPress sites for the Leyka plugin and record installed versions.
  • If Leyka is <= 3.29.2, check vendor or Patchstack guidance for a fixed release.
  • Update to a vendor-supported fixed version if one is available.
  • Disable or remove Leyka where no supported fix is available.
  • Review affected pages for unexpected script content or unauthorized changes.

Validation and detection

  • Confirm Leyka plugin version from WordPress admin or asset inventory.
  • Verify whether public Leyka forms accept unauthenticated user-controlled input.
  • Review CMS content, donation records, and plugin fields for suspicious script-like content.
  • Check web and admin logs for unusual submissions around Leyka workflows.
  • Document remediation evidence, including version, date, and affected site list.
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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-27450 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-27450Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
Teplitsa of social technologiesLeykaleyka, n/aunaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.