CERTA-2007-AVI-034
Vulnerability from certfr_avis - Published: - Updated:
Wordpress est une plateforme de publication web écrite en langage PHP. Des vulnérabilités permettent des atteintes à la disponibilité et à l'intégrité des données.
Description
Les vulnérabilités sont de plusieurs ordres :
- une vulnérabilité dans wp-admin/templates.php permet l'injection de scripts ou de code HTML ;
- lorsque le paramétrage PHP active l'option mbstring, une personne malintentionnée peut contourner le système de protection des requêtes SQL et ainsi exécuter des commandes SQL arbitraires ;
- les messages d'erreur retournés par wp-login.php sont différents selon l'existence ou non de l'utilisateur, ce qui facilite la préparation d'attaques par recherche exhaustive.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Wordpress, versions 2.0.6 et antérieures.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cSPAN class=\"textit\"\u003eWordpress\u003c/SPAN\u003e, versions 2.0.6 et ant\u00e9rieures.",
"content": "## Description\n\nLes vuln\u00e9rabilit\u00e9s sont de plusieurs ordres :\n\n- une vuln\u00e9rabilit\u00e9 dans wp-admin/templates.php permet l\u0027injection de\n scripts ou de code HTML ;\n- lorsque le param\u00e9trage PHP active l\u0027option mbstring, une personne\n malintentionn\u00e9e peut contourner le syst\u00e8me de protection des\n requ\u00eates SQL et ainsi ex\u00e9cuter des commandes SQL arbitraires ;\n- les messages d\u0027erreur retourn\u00e9s par wp-login.php sont diff\u00e9rents\n selon l\u0027existence ou non de l\u0027utilisateur, ce qui facilite la\n pr\u00e9paration d\u0027attaques par recherche exhaustive.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2006-6808",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-6808"
},
{
"name": "CVE-2007-0109",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-0109"
},
{
"name": "CVE-2007-0107",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-0107"
}
],
"links": [
{
"title": "Bulletin de Wordpress du 15 janvier 2007 :",
"url": "http://wordpress.org/"
}
],
"reference": "CERTA-2007-AVI-034",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-01-17T00:00:00.000000"
}
],
"risks": [
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "\u003cspan class=\"textit\"\u003eWordpress\u003c/span\u003e est une plateforme de publication\nweb \u00e9crite en langage PHP. Des vuln\u00e9rabilit\u00e9s permettent des atteintes \u00e0\nla disponibilit\u00e9 et \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es.\n",
"title": "Vuln\u00e9rabilit\u00e9 de Wordpress",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin Wordpress du 15 janvier 2007",
"url": null
}
]
}
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.