CVE-2006-4743

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 2%CVSS: Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

WordPress 2.0.2 through 2.0.5 allows remote attackers to obtain sensitive information via a direct request for (1) 404.php, (2) akismet.php, (3) archive.php, (4) archives.php, (5) attachment.php, (6) blogger.php, (7) comments.php, (8) comments-popup.php, (9) dotclear.php, (10) footer.php, (11) functions.php, (12) header.php, (13) hello.php, (14) wp-content/themes/default/index.php, (15) links.php, (16) livejournal.php, (17) mt.php, (18) page.php, (19) rss.php, (20) searchform.php, (21) search.php, (22) sidebar.php, (23) single.php, (24) textpattern.php, (25) upgrade-functions.php, (26) upgrade-schema.php, or (27) wp-db-backup.php, which reveal the path in various error messages. NOTE: another researcher has disputed the details of this report, stating that version 2.0.5 does not exist. NOTE: the admin-footer.php, admin-functions.php, default-filters.php, edit-form-advanced.php, edit-link-form.php, edit-page-form.php, kses.php, locale.php, rss-functions.php, template-loader.php, and wp-db.php vectors are already covered by CVE-2006-0986. The edit-form-comment.php, vars.php, and wp-settings.php vectors are already covered by CVE-2005-4463. The menu-header.php vector is already covered by CVE-2005-2110.

CVSS v3
EG Score
0.0(none)
EPSS
82.2%
KEV
Not listed

Published

September 13, 2006

Last Modified

April 16, 2026

Data Freshness Timeline

(refreshed 5× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 22:25 UTCEPSS rescore
  2. 2026-07-13 06:07 UTCEPSS rescore
  3. 2026-07-13 06:07 UTCEPSS rescore
  4. 2026-07-08 19:15 UTCOSV refresh
  5. 2026-07-08 15:09 UTCEPSS rescore
  6. 2026-07-06 02:19 UTCEPSS rescore
  7. 2026-07-06 02:19 UTCEPSS rescore
  8. 2026-07-05 02:26 UTCEPSS rescore
  9. 2026-07-04 06:27 UTCEPSS rescore
  10. 2026-07-04 06:26 UTCEPSS rescore
  11. 2026-07-02 14:00 UTCEPSS rescore
  12. 2026-07-01 15:02 UTCEPSS rescore
  13. 2026-07-01 15:02 UTCEPSS rescore
  14. 2026-06-30 23:18 UTCEPSS rescore
  15. 2026-06-28 14:02 UTCEPSS rescore
  16. 2026-06-28 04:52 UTCEPSS rescore
  17. 2026-06-25 13:46 UTCEPSS rescore
  18. 2026-06-25 13:46 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-24 14:01 UTCEPSS rescore
  21. 2026-06-23 21:29 UTCEPSS rescore
  22. 2026-06-23 21:29 UTCEPSS rescore
  23. 2026-06-21 01:56 UTCEPSS rescore
  24. 2026-06-21 01:56 UTCEPSS rescore
  25. 2026-06-21 01:56 UTCEPSS rescore
Show 55 more
  1. 2026-06-20 07:12 UTCOSV refresh
  2. 2026-06-19 19:22 UTCEPSS rescore
  3. 2026-06-19 19:22 UTCEPSS rescore
  4. 2026-06-18 17:49 UTCEPSS rescore
  5. 2026-06-18 17:49 UTCEPSS rescore
  6. 2026-06-17 17:49 UTCEPSS rescore
  7. 2026-06-17 17:49 UTCEPSS rescore
  8. 2026-06-16 17:49 UTCEPSS rescore
  9. 2026-06-16 17:49 UTCEPSS rescore
  10. 2026-06-15 17:44 UTCEPSS rescore
  11. 2026-06-14 23:13 UTCEPSS rescore
  12. 2026-06-13 22:57 UTCEPSS rescore
  13. 2026-06-13 22:57 UTCEPSS rescore
  14. 2026-06-12 23:08 UTCEPSS rescore
  15. 2026-06-08 14:13 UTCEPSS rescore
  16. 2026-06-07 15:21 UTCEPSS rescore
  17. 2026-06-07 15:21 UTCEPSS rescore
  18. 2026-06-06 13:44 UTCEPSS rescore
  19. 2026-06-06 13:44 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-06-05 06:07 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-04 13:09 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
  26. 2026-06-02 20:10 UTCEPSS rescore
  27. 2026-06-01 13:49 UTCEPSS rescore
  28. 2026-06-01 13:49 UTCEPSS rescore
  29. 2026-05-31 22:28 UTCEPSS rescore
  30. 2026-05-31 22:28 UTCEPSS rescore
  31. 2026-05-31 06:48 UTCEG score recompute
  32. 2026-05-31 06:48 UTCGHSA enrichment
  33. 2026-05-31 00:13 UTCEPSS rescore
  34. 2026-05-31 00:13 UTCEPSS rescore
  35. 2026-05-29 13:40 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-28 13:42 UTCEPSS rescore
  38. 2026-05-27 13:37 UTCEPSS rescore
  39. 2026-05-27 13:37 UTCEPSS rescore
  40. 2026-05-26 13:41 UTCEPSS rescore
  41. 2026-05-26 13:41 UTCEPSS rescore
  42. 2026-05-26 07:16 UTCEPSS rescore
  43. 2026-05-26 07:16 UTCEPSS rescore
  44. 2026-05-26 07:16 UTCEPSS rescore
  45. 2026-05-24 16:42 UTCEPSS rescore
  46. 2026-05-22 23:25 UTCOSV refresh
  47. 2026-05-22 21:15 UTCEPSS rescore
  48. 2026-05-22 21:15 UTCEPSS rescore
  49. 2026-05-22 21:15 UTCEPSS rescore
  50. 2026-05-21 22:38 UTCEPSS rescore
  51. 2026-05-20 22:36 UTCEPSS rescore
  52. 2026-05-20 11:20 UTCEPSS rescore
  53. 2026-05-20 11:20 UTCEPSS rescore
  54. 2026-05-18 21:29 UTCEPSS rescore
  55. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2006-4743?
CVE-2006-4743 is a none vulnerability published on September 13, 2006. WordPress 2.0.2 through 2.0.5 allows remote attackers to obtain sensitive information via a direct request for (1) 404.php, (2) akismet.php, (3) archive.php, (4) archives.php, (5) attachment.php, (6) blogger.php, (7) comments.php, (8) comments-popup.php, (9) dotclear.php, (10) footer.php, (11)…
When was CVE-2006-4743 disclosed?
CVE-2006-4743 was first published in the National Vulnerability Database on September 13, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-4743 actively exploited?
CVE-2006-4743 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 82.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2006-4743?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-4743, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2006-4743

Explore →

Is Your Infrastructure Affected by CVE-2006-4743?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.