dbcve.org
Single User ChatWordPress extension · Aakashbhagat

CVE-2024-13646

HIGH · 8.1 CVSS v3.1 Published 2025-01-30
Fix available
A fix is available. Upgrade to after 0.5 or later.
See remediation →
87/100
Remediation priority · High
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 Single-user-chat plugin for WordPress is vulnerable to unauthorized modification of data that can lead to a denial of service due to insufficient validation on the 'single_user_chat_update_login' function in all versions up to, and including, 0.5. This makes it possible for authenticated attackers, with subscriber-level access and above, to update option values to 'login' on the WordPress site. This may be leveraged to update an option that would create an error on the site and deny service to legitimate users or be used to set some values to true such as registration.

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 Single-user-chat WordPress plugin has a missing authorization and input validation vulnerability in the single_user_chat_update_login function. Authenticated users with subscriber-level permissions can manipulate WordPress options to arbitrary values, specifically 'login', causing errors and denial of service, or enabling dangerous settings like user registration.

MitigationIf a patched version is available, update immediately. If not, disable and remove the plugin as it appears to be unmaintained (version 0.5), and consider replacing with a secure alternative or implementing custom code with proper security controls.

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
Single User ChatWordPress extension
Affected:<= 0.5

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 plugin is installed
    Go to WordPress admin > Plugins and check if 'Single User Chat' by Aakashbhagat is installed and active
    Affected if The plugin is installed and active
  2. Check the installed version
    In WordPress admin > Plugins, find the Single User Chat plugin and note the version number displayed
    Affected if Version is 0.5 or lower (the vulnerable version range)
  3. Confirm subscriber-level access exists
    Navigate to WordPress admin > Users > All Users and check if any users exist with the 'Subscriber' role
    Affected if Any subscriber-level accounts exist in the system
  4. Test for the vulnerable function exposure
    Check if the plugin exposes an AJAX or admin action endpoint for 'single_user_chat_update_login' - this typically appears in the plugin's PHP files under wp-content/plugins/single-user-chat/
    Affected if The vulnerable function single_user_chat_update_login is present in the plugin code and is callable without proper capability checks

You are affected if the Single User Chat plugin version 0.5 or lower is installed and active on your WordPress site, especially if you have any subscriber-level user accounts enabled.

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 0.5
Interim mitigation

If a patched version is available, update immediately. If not, disable and remove the plugin as it appears to be unmaintained (version 0.5), and consider replacing with a secure alternative or implementing custom code with proper security controls.

Recommended fix Moderate confidence

Latest version of Single User Chat plugin (version > 0.5)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Single User Chat plugin
  4. Check if an update is available and update to the latest version beyond 0.5
  5. Verify the update was applied successfully

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

Fix this in Single User Chat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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