LiveActive security incident?Get immediate response
CVE Record

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

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

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-39314 is an unauthenticated reflected cross-site scripting flaw in the WordPress Leyka plugin through version 3.30.2. A victim must interact with attacker-controlled content. Successful exploitation could run script in the victim’s browser and affect confidentiality, integrity, and availability at low levels.

Executive priority

High priority only where Leyka is installed on public WordPress sites. This is not confirmed actively exploited in the provided sources, but unauthenticated reflected XSS on public web properties can create reputational and account-risk exposure.

Technical view

The source describes CWE-79 reflected XSS in Teplitsa of social technologies Leyka for WordPress, package name leyka, <=3.30.2. CVSS 3.1 is 7.1: network reachable, low complexity, no privileges required, user interaction required, changed scope, and low C/I/A impact.

Likely exposure

Public WordPress sites using the Leyka plugin at version 3.30.2 or earlier are the likely exposed population. Evidence does not define affected CPEs or detailed vulnerable endpoints.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The risk is still meaningful because exploitation is unauthenticated, network reachable, and could target users through crafted links or pages.

Researcher notes

The bundle lacks endpoint, parameter, proof-of-concept, fixed-version, and exploit-observation details. Avoid assuming more than reflected XSS in Leyka <=3.30.2. Validate exposure through asset inventory and version checks, not exploit reproduction.

Mitigation direction

  • Inventory WordPress sites for the Leyka plugin and exact installed version.
  • Treat Leyka <=3.30.2 as vulnerable based on the cited record.
  • Check vendor, WordPress plugin, or Patchstack guidance for the corrected version.
  • Upgrade, remove, or disable Leyka where vendor guidance confirms remediation.
  • Prioritize public donation sites and administrator-facing workflows first.

Validation and detection

  • Confirm whether Leyka is installed on each WordPress property.
  • Record the installed Leyka version and compare it with <=3.30.2.
  • Review web logs for suspicious requests targeting Leyka parameters or pages.
  • Verify remediation against vendor or Patchstack guidance after updating.
  • Confirm no business-critical public forms broke after remediation.
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-39314 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-39314Attack 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.