For The Visually ImpairedWordPress extension · 984.ru
CVE-2023-25038
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in 984.Ru For the visually impaired plugin <= 0.58 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the 984.Ru For the visually impaired WordPress plugin version 0.58 and earlier. The vulnerability allows attackers to induce authenticated users to perform unwanted actions by tricking them into submitting malicious requests.
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
For The Visually ImpairedWordPress extension
<= 0.58CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the 984.ru For The Visually Impaired plugin is installedCheck your WordPress plugins directory (wp-content/plugins/) for a folder named '984ru-for-the-visually-impaired' or similar, or view installed plugins in WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin, find the plugin in the plugins list and check the version column, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block, or run: grep -r 'Version:' wp-content/plugins/ | grep -i visuallyAffected if The version number is 0.58 or lower (e.g., 0.55, 0.56, 0.57, 0.58)
-
Verify if state-changing operations lack anti-CSRF protectionsExamine the main plugin PHP files for forms and action handlers. Search for state-changing functions (POST/GET requests that modify data) and check if they use wp_verify_nonce(), check_ajax_referer(), or similar nonce verification functions. Look for missing nonce fields in forms.Affected if Any admin or user-facing form/action in the plugin processes requests without validating nonces or checking referer/origin headers
You are affected if the 984.ru For The Visually Impaired plugin is installed with version 0.58 or lower AND contains forms or actions that process requests without CSRF token validation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens (nonces) on all state-changing operations and validate request referer/origin headers. Update to a patched version if available.
Fix this in For The Visually Impaired
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25038 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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