CVE-2023-4917

Leyka <= 3.30.7 - Authenticated (Subscriber+) Sensitive Information Exposure

2023-09-12 00:00

Strategic Overview

Status: Patched in 3.30.7.1
Affected Plugin: Leyka
Affected Version: <= 3.30.7
CVSS: 5.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2023-4917

At a glance

CVE-2023-4917 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Leyka WordPress plugin, affecting versions <= 3.30.7. It carries a CVSS score of 5.3 (reachable over the network; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.30.7.1; sites on affected versions should update now. Disclosed September 2023, reported by István Márton.

Vulnerability Overview

The Leyka plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.30.7 via the 'leyka_ajax_get_env_and_options' function. This can allow authenticated attackers with subscriber-level permissions or above to extract sensitive data including Sberbank API key and password, PayPal Client Secret, and more keys and passwords.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Leyka <= 3.30.7 carries this weakness at leyka_ajax_get_env_and_options, and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Leyka the fix is 3.30.7.1: builds <= 3.30.7 are affected, anything from 3.30.7.1 onward is not.

Remediation

Update to version 3.30.7.1, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Leyka 3.30.7.1 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-4917 https://www.wordfence.com/threat-intel/vulnerabilities/id/dcd24b90-94ff-4625-8e3e-9c90e38683f9 https://nvd.nist.gov/vuln/detail/CVE-2023-4917

Related records

Other vulnerabilities in Leyka

CVSS Vector

5.3

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

Base

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/