CERTFR-2025-ALE-008
Vulnerability from certfr_alerte - Published: 2025-06-05 - Updated: 2025-07-21
[Mise à jour du 06 juin 2025]
Une preuve de concept est publiquement disponible.
[Publication initiale]
Le 01 juin 2025, Roundcube a publié des correctifs concernant une vulnérabilité critique affectant son portail de messagerie ainsi que tous les produits l'incluant (par exemple cPanel et Plesk).
Cette vulnérabilité permet à un utilisateur authentifié d'exécuter du code arbitraire à distance.
L'éditeur ne mentionne pas d'identifiant CVE.
Des détails techniques sur cette vulnérabilité ont été publiés avec l'identifiant CVE-2025-49113. Le CERT-FR anticipe la disponibilité imminente de codes d'exploitation et recommande fortement de mettre à jour dans les plus brefs délais au vu du nombre important de produits exposés.
Solutions
Les versions correctives 1.5.10 et 1.6.11 ont été publiées par l'éditeur.
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| Roundcube | Roundcube Webmail | Roundcube Webmail versions 1.6.x antérieures à 1.6.11 | ||
| Roundcube | Roundcube Webmail | Roundcube Webmail versions antérieures à 1.5.10 |
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Roundcube Webmail versions 1.6.x ant\u00e9rieures \u00e0 1.6.11",
"product": {
"name": "Roundcube Webmail",
"vendor": {
"name": "Roundcube",
"scada": false
}
}
},
{
"description": "Roundcube Webmail versions ant\u00e9rieures \u00e0 1.5.10",
"product": {
"name": "Roundcube Webmail",
"vendor": {
"name": "Roundcube",
"scada": false
}
}
}
],
"affected_systems_content": "",
"closed_at": "2025-07-21",
"content": "## Solutions\n\nLes versions correctives 1.5.10 et 1.6.11 ont \u00e9t\u00e9 publi\u00e9es par l\u0027\u00e9diteur.\n\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2025-49113",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-49113"
}
],
"initial_release_date": "2025-06-05T00:00:00",
"last_revision_date": "2025-07-21T00:00:00",
"links": [
{
"title": "Avis CERT-FR CERTFR-2025-AVI-0468 du 02 juin 2025",
"url": "https://cert.ssi.gouv.fr/avis/CERTFR-2025-AVI-0468/"
}
],
"reference": "CERTFR-2025-ALE-008",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2025-06-05T00:00:00.000000"
},
{
"description": "Une preuve de concept est publiquement disponible.",
"revision_date": "2025-06-06T00:00:00.000000"
},
{
"description": " Cl\u00f4ture de l\u0027alerte. Cela ne signifie pas la fin d\u0027une menace. Seule l\u0027application de la mise \u00e0 jour permet de vous pr\u00e9munir contre l\u0027exploitation de la vuln\u00e9rabilit\u00e9 correspondante.",
"revision_date": "2025-07-21T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "\u003cspan class=\"important-content\"\u003e\u003cb\u003e[Mise \u00e0 jour du 06 juin 2025]\u003c/b\u003e\u003c/span\u003e\u003c/br\u003e\nUne preuve de concept est publiquement disponible.\n\n[Publication initiale]\u003c/br\u003e\nLe 01 juin 2025, Roundcube a publi\u00e9 des correctifs concernant une vuln\u00e9rabilit\u00e9 critique affectant son portail de messagerie ainsi que tous les produits l\u0027incluant (par exemple cPanel et Plesk).\n\nCette vuln\u00e9rabilit\u00e9 permet \u00e0 un utilisateur authentifi\u00e9 d\u0027ex\u00e9cuter du code arbitraire \u00e0 distance.\n\nL\u0027\u00e9diteur ne mentionne pas d\u0027identifiant CVE.\n\nDes d\u00e9tails techniques sur cette vuln\u00e9rabilit\u00e9 ont \u00e9t\u00e9 publi\u00e9s avec l\u0027identifiant\u00a0CVE-2025-49113. Le CERT-FR anticipe la disponibilit\u00e9 imminente de codes d\u0027exploitation et recommande fortement de mettre \u00e0 jour dans les plus brefs d\u00e9lais au vu du nombre important de produits expos\u00e9s.",
"title": "[M\u00e0J] Vuln\u00e9rabilit\u00e9 dans Roundcube",
"vendor_advisories": [
{
"published_at": "2025-06-01",
"title": "Bulletin de s\u00e9curit\u00e9 Roundcube security-updates-1.6.11-and-1.5.10",
"url": "https://roundcube.net/news/2025/06/01/security-updates-1.6.11-and-1.5.10"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.