dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 13 Mar 2026.
Debian LinuxOperating system · Debian

CVE-2025-49113

HIGH · 8.8 CVSS v3.1 Published 2025-06-02
Fix available
A fix is available. Upgrade to 1.5.10 / 1.6.11 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable Zero-click Patch available

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
Roundcube Webmail before 1.5.10 and 1.6.x before 1.6.11 allows remote code execution by authenticated users because the _from parameter in a URL is not validated in program/actions/settings/upload.php, leading to PHP Object Deserialization.

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

Roundcube Webmail versions before 1.5.10 and 1.6.11 contain a PHP Object Deserialization vulnerability in program/actions/settings/upload.php. The unvalidated _from parameter in a URL allows authenticated users to achieve remote code execution.

MitigationUpgrade Roundcube Webmail to version 1.5.10 or 1.6.11 or later to patch the deserialization vulnerability. As an authenticated-user RCE with high CVSS, this should be prioritized.

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
Debian LinuxOperating system
Affected:= 11.0
WebmailApplication
Affected:< 1.5.10>= 1.6.0, < 1.6.11

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Roundcube Webmail version
    Check the Roundcube version file (e.g., program/include/iniset.php or version in the UI's About section), or run 'dpkg -l | grep roundcube' on Debian systems
    Affected if Version is below 1.5.10, or between 1.6.0 and 1.6.11 inclusive
  2. Confirm the vulnerable upload.php file exists
    Locate program/actions/settings/upload.php in the Roundcube installation directory and verify it is present and accessible
    Affected if The file exists in the installation (vulnerable code path is present)
  3. Check if settings/upload functionality is accessible to authenticated users
    Review Roundcube's access controls and verify whether authenticated users can access the settings/upload action; test accessing the endpoint with a valid authenticated session
    Affected if Authenticated users can access the settings/upload functionality (the vulnerability is exploitable)
  4. Verify the _from parameter handling in upload.php
    Inspect the upload.php source code and confirm that the _from parameter from the request is passed to an unserialize() call without proper validation
    Affected if The _from parameter is processed through unserialize() without sanitization

A user is affected if they run a Roundcube version below 1.5.10 or between 1.6.0-1.6.11, the vulnerable upload.php file exists, authenticated users can access the settings/upload action, and the _from parameter is deserialized without validation.

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 1.5.10 / 1.6.11 or later
Fixed in 1.5.101.6.11
Vendor patch github.com →
Interim mitigation

Upgrade Roundcube Webmail to version 1.5.10 or 1.6.11 or later to patch the deserialization vulnerability. As an authenticated-user RCE with high CVSS, this should be prioritized.

Recommended fix High confidence

Roundcube Webmail 1.5.10 or 1.6.11 (depending on your current major version branch)

  1. Backup the current Roundcube Webmail installation and database before proceeding
  2. For Debian 11.0: Run 'apt update && apt install roundcube-webmail' to install the patched package from Debian repositories
  3. For manual installations: Download Roundcube Webmail 1.5.10 or 1.6.11 from the official repository at github.com/roundcube/roundcubemail
  4. Extract the new version and replace the existing files, preserving config/ directory and any custom plugins
  5. Run database updates if required: php bin/updatedb.sh
  6. Clear template and cache directories: rm -rf temp/* cache/*
  7. Verify the upgrade by logging in and checking the About page shows the correct version
Caveat Security-focused upgrade with no major breaking changes expected; always test in staging first

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

Fix this in Debian Linux Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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