dbcve.org
LeykaWordPress extension · Te St

CVE-2023-4917

MEDIUM · 6.5 CVSS v3.1 Published 2023-09-13
Fix available
A fix is available. Upgrade to after 3.30.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Leyka WordPress plugin up to version 3.30.7 contains an insecure direct object reference in the 'leyka_ajax_get_env_and_options' AJAX function that allows any authenticated user with subscriber-level permissions to retrieve sensitive configuration data including Sberbank API credentials, PayPal Client Secret, and additional API keys and passwords.

MitigationUpdate Leyka plugin to version 3.30.8 or later which contains the patch for this sensitive information exposure vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LeykaWordPress extension
Affected:<= 3.30.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Leyka plugin installation
    Check your WordPress site for the Leyka plugin in wp-admin under Plugins, or inspect the /wp-content/plugins/leyka directory if you have file system access.
    Affected if Leyka plugin is present on the WordPress site.
  2. Determine installed Leyka version
    In WordPress wp-admin under Plugins > Installed Plugins, find the Leyka plugin and note the version number displayed. Alternatively, check the main plugin PHP file header for the Version field.
    Affected if The installed version is 3.30.3 or lower.
  3. Confirm subscriber-level user accounts exist
    In WordPress wp-admin under Users, review the user list and check if any accounts have the Subscriber role assigned.
    Affected if At least one user with Subscriber role exists on the site.
  4. Check for sensitive API credentials in Leyka settings
    In WordPress wp-admin, navigate to Leyka plugin settings and examine fields for Sberbank API credentials, PayPal Client Secret, or other API keys and passwords that may be stored in the configuration.
    Affected if Sensitive API credentials or secrets are stored in the Leyka plugin configuration.

The environment is affected if the Leyka plugin version is 3.30.3 or lower and the plugin has sensitive API credentials configured, because any authenticated subscriber-level user could retrieve them via the vulnerable AJAX function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.30.3
Interim mitigation

Update Leyka plugin to version 3.30.8 or later which contains the patch for this sensitive information exposure vulnerability.

Recommended fix Moderate confidence

Leyka version 3.30.8 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Leyka plugin
  4. Check if an update is available and update to the latest version (version 3.30.8 or later based on the vulnerability description in version 3.30.7)
  5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. After updating, verify the site still functions correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Leyka Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4917 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4917 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data