dbcve.org
Original Texts Yandex WebmasterWordPress extension · Zixn

CVE-2023-46775

HIGH · 8.8 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to after 1.18 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Djo Original texts Yandex WebMaster plugin <= 1.18 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Djo Original texts Yandex WebMaster WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions by forging malicious requests.

MitigationUpdate the plugin to version 1.19 or later. If immediate update is not possible, implement WordPress nonce verification on all plugin forms and admin action handlers.

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
Original Texts Yandex WebmasterWordPress extension
Affected:<= 1.18

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the Yandex Webmaster plugin is installed
    Check for the plugin directory at wp-content/plugins/zixn-original-texts-yandex-webmaster or search for 'Yandex Webmaster' in the WordPress plugins list at /wp-admin/plugins.php
    Affected if The plugin directory or listing exists in the WordPress installation
  2. Determine the installed plugin version
    Open the main plugin file (usually named zixn-original-texts-yandex-webmaster.php) and look for the 'Version:' field in the plugin header comment at the top of the file
    Affected if The reported version number is 1.18 or lower
  3. Confirm plugin is active
    Navigate to /wp-admin/plugins.php and check if the Yandex Webmaster plugin shows as 'Active'
    Affected if The plugin is activated and accessible to authenticated administrators
  4. Verify admin access exists
    Check for existing administrator-level WordPress users who have access to the plugin settings at /wp-admin/admin.php?page=yandex-webmaster
    Affected if There are authenticated administrators who can access the plugin admin interface

The environment is affected if the Zixn Original Texts Yandex Webmaster plugin version 1.18 or lower is installed and active, exposing admin users to CSRF attacks through unauthenticated form submissions.

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.

From vendor data
Upgrade available Upgrade to a release after 1.18
Interim mitigation

Update the plugin to version 1.19 or later. If immediate update is not possible, implement WordPress nonce verification on all plugin forms and admin action handlers.

Fix this in Original Texts Yandex Webmaster Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46775 — 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-46775 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