CVE-2025-30949
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 · uneditedDeserialization of Untrusted Data vulnerability in Guru Team Site Chat on Telegram site-chat-on-telegram allows Object Injection.This issue affects Site Chat on Telegram: from n/a through <= 1.0.4.
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 confidenceA deserialization of untrusted data vulnerability in the Guru Team Site Chat on Telegram WordPress plugin (versions <= 1.0.4) allows attackers to inject arbitrary PHP objects, potentially leading to remote code execution if suitable magic methods exist in the application.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Verify Site Chat on Telegram plugin is installedCheck if the plugin directory exists in wp-content/plugins/ (common names: site-chat-on-telegram, guru-team-site-chat-on-telegram, or similar). Use WP-CLI: wp plugin list --status=active --field=name | grep -i telegramAffected if The plugin directory or an active plugin with 'telegram' in the name exists in the WordPress installation
-
Determine installed plugin versionRead the main plugin PHP file header for the Version field. Common path: wp-content/plugins/[plugin-folder]/[plugin-file].php. Run: grep -i 'Version:' wp-content/plugins/*/site-chat-on-telegram*.phpAffected if The plugin version displayed is 1.0.4 or any version lower than 1.0.4
-
Confirm the plugin processes external Telegram dataInspect the plugin code for functions that handle incoming data from Telegram (webhook handlers, REST API endpoints, or callback functions). Look for: register_rest_route calls, wp_ajax_ hooks, or parse_request functions that receive $_GET/$_POST data from TelegramAffected if The plugin has active endpoints that accept and process data from Telegram servers without sanitization
-
Verify deserialization usage in the pluginSearch the plugin source code for unserialize() calls that operate on input data. Run: grep -rn 'unserialize' wp-content/plugins/[plugin-folder]/Affected if The plugin code contains unserialize() calls operating on data that originates from unauthenticated user input
If the Site Chat on Telegram plugin is installed at version 1.0.4 or lower and processes Telegram webhook data, the environment is vulnerable to CVE-2025-30949.
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 to the latest version of Site Chat on Telegram if a patch is available; otherwise disable the plugin until a fix is released, as deserialization vulnerabilities can be exploited without authentication.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30949 — 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-2025-30949 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