CVE-2006-2667: n/a vulnerability

CVE-2006-2667: Direct static code injection vulnerability in WordPress 2.0.2 and earlier allows remote attackers to execut...

Direct static code injection vulnerability in WordPress 2.0.2 and earlier allows remote attackers to execute arbitrary commands by inserting a carriage return and PHP code when updating a profile, which is appended after a special comment sequence into files in (1) wp-content/cache/userlogins/ (2) wp-content/cache/users/ which are later included by cache.php, as demonstrated using the displayname argument.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 17:58 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2006-2667 affects WordPress 2.0.2 and earlier. A remote attacker could abuse profile updates so attacker-controlled PHP is written into cached user files that WordPress later loads. In business terms, an exposed legacy WordPress site could become a server compromise, not just a website defacement issue. Exposure is likely limited to very old WordPress deployments, specifically WordPress 2.0.2 and earlier. Modern managed WordPress should not be assumed affected from these sources. Risk remains for abandoned sites, restored legacy images, old distribution packages, or internet-facing archives still running the vulnerable code. Prioritize remediation if any legacy WordPress 2.0.2 or earlier instance is reachable. The affected software is obsolete, and the impact is server-side command execution. If no such legacy deployment exists, this should be documented as not applicable rather than tracked as an urgent current-platform issue. Mitigation focus: Identify and retire WordPress 2.0.2 or earlier instances.; Check WordPress and distribution advisories for the correct fixed upgrade path.; Migrate legacy sites to supported WordPress versions and maintained PHP stacks..

Prepared: Jun 29, 2026, 12:30 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2006-2667 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: May 30, 2006, 21:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
wordpress-user-profile-code-injection(26687)CVE reference · vdb-entry, x_refsource_XF

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.