Skip to content
WatchlistHigh

CVE-2006-5085Pixel Motion Blog Vulnerability

Static code injection vulnerability in config.php in Blog Pixel Motion 2.1.1 allows remote attackers to execute arbitrary PHP code via the nom_blog parameter, which is injected into include/variables.php.

Published Sep 28, 2006 · Updated Apr 22, 2026

Key Facts

Patch immediately
  • CVE-2006-5085 is a high-severity vulnerability (CVSS 7.5 v2) affecting Pixel Motion Blog.
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 47% probability of exploitation in the next 30 days.
  • No fixed version is listed yet; check the vendor advisory for mitigations.
  • Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Scores

CVSS v2

7.5

AV:N/AC:L/Au:N/C:P/I:P/A:P

EPSS (30-day exploit likelihood)

47%

Higher than 98.8% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

40/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

1

Proof-of-concept links

In-the-wild evidence

2

Reports of active use

Advisories And Exploit References

Description

Static code injection vulnerability in config.php in Blog Pixel Motion 2.1.1 allows remote attackers to execute arbitrary PHP code via the nom_blog parameter, which is injected into include/variables.php.

Affected Products

1 affected entries in total
ProductAffected versionsFixed in
Pixel Motion BlogPixel Motion2.1.1n/a

Timeline

  1. Publicly disclosed

    Sep 28, 2006

  2. Last updated

    Apr 22, 2026

References

2 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2006-5085 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.