dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2026-1233

HIGH · 7.5 CVSS v3.1 Published 2026-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Text to Speech for WP (AI Voices by Mementor) plugin for WordPress is vulnerable to sensitive information exposure in all versions up to, and including, 1.9.8. This is due to the plugin containing hardcoded MySQL database credentials for the vendor's external telemetry server in the `Mementor_TTS_Remote_Telemetry` class. This makes it possible for unauthenticated attackers to extract and decode these credentials, gaining unauthorized write access to the vendor's telemetry database.

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 Text to Speech for WP (AI Voices by Mementor) WordPress plugin versions up to 1.9.8 contains hardcoded MySQL database credentials in the Mementor_TTS_Remote_Telemetry class, exposing the vendor's external telemetry server database credentials to unauthenticated attackers who can extract and decode them.

MitigationUpdate the plugin to a patched version or remove the plugin entirely. The vendor must immediately rotate the exposed credentials and implement secure credential management rather than hardcoding them.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the Text to Speech for WP plugin
    Access your WordPress plugins directory (wp-content/plugins/) and look for a folder named 'text-to-speech-wp', 'tts-wp', or similar. Check the plugin's main PHP file for the version number in the plugin header.
    Affected if The plugin is installed and the version does not include the hardcoded credential fix (version 1.9.9 or later), or the version cannot be determined.
  2. Find the Mementor_TTS_Remote_Telemetry class
    Search the plugin directory for files containing the string 'Mementor_TTS_Remote_Telemetry'. This class is where the hardcoded credentials are stored.
    Affected if The Mementor_TTS_Remote_Telemetry class exists in the plugin files.
  3. Inspect the class for hardcoded database credentials
    Open the file containing Mementor_TTS_Remote_Telemetry and search within that class for hardcoded MySQL connection strings, username/password arrays, or credential variables. Look for strings resembling database host, user, and password definitions.
    Affected if Hardcoded MySQL credentials (host, username, password) are found defined as literal strings or arrays within the Mementor_TTS_Remote_Telemetry class.
  4. Verify unauthenticated access to telemetry functionality
    Check if the Mementor_TTS_Remote_Telemetry class methods are accessible without authentication. Review the class for public methods that handle database operations and determine if they require any authentication or capability checks.
    Affected if The telemetry class methods can be called by unauthenticated users (no require_login, capability checks, or nonce verification on the relevant methods).

If the Text to Speech for WP plugin is installed with the Mementor_TTS_Remote_Telemetry class containing hardcoded MySQL credentials accessible to unauthenticated users, the environment is affected by CVE-2026-1233.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version or remove the plugin entirely. The vendor must immediately rotate the exposed credentials and implement secure credential management rather than hardcoding them.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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