CVE-2024-10390
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 · uneditedThe Elfsight Telegram Chat CC plugin for WordPress is vulnerable to unauthorized modification of data to a missing capability check on the 'updatePreferences' function in all versions up to, and including, 1.1.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe Elfsight Telegram Chat CC WordPress plugin has a missing capability check on the 'updatePreferences' function in versions up to 1.1.0. This allows any authenticated user with subscriber-level access to call this function and inject arbitrary JavaScript through the preferences, leading to stored XSS when other users access affected pages.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Elfsight Telegram Chat CC plugin is installedLog in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Elfsight Telegram Chat CC' in the list. Note its activation status.Affected if The plugin is installed and activated
-
Check the installed plugin versionIn the Plugins list, click on the plugin details link or view the plugin header comment in the main plugin file (typically in wp-content/plugins/elfsight-telegram-chat-cc/). Compare the version number to 1.1.0.Affected if The installed version is 1.1.0 or earlier (versions up to and including 1.1.0 are affected)
-
Inspect the updatePreferences function for capability checksOpen the main plugin PHP file and locate the 'updatePreferences' function. Examine the code for a capability check (such as current_user_can('manage_options') or similar admin-level permission) before executing the function logic.Affected if No capability check exists, or the check allows subscriber-level access (any authenticated user can execute)
-
Verify if the plugin preferences can be modified by low-privilege usersUsing a test account with subscriber-level access, attempt to access the plugin settings page or trigger an AJAX action that calls updatePreferences. Check if the request succeeds without permission errors.Affected if Subscriber-level or other low-privilege users can successfully modify preferences
If the plugin is installed at version 1.1.0 or earlier and the updatePreferences function lacks a proper capability check, the environment is affected by this stored XSS vulnerability.
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 dataUpdate the plugin to version 1.1.1 or later which includes the proper capability check. If an update is unavailable, add a capability check (e.g., current_user_can('manage_options')) to the updatePreferences function.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-10390 — 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-2024-10390 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