CVE-2006-7002: Cross-site scripting (XSS) vulnerability in add_comment.php in Wheatblog (wB) 1.1 allows remote attackers to i

Routine

MEDIUM 4.3DOWNGRADE

CVE-2006-7002 is a medium-severity flaw (CVSS 4.3) affecting wheatblog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Cross-site scripting (XSS) vulnerability in add_comment.php in Wheatblog (wB) 1.1 allows remote attackers to inject arbitrary web script or HTML via the Email field. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information. NOTE: this issue may overlap CVE-2006-5195.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.3 (Medium)
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Published	2007-02-12
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: wheatblog

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2007-02-12 19:28 UTCPublished CVE record published
2026-06-16 22:34 UTCUpdated Record last modified

wheatblog wheatblog DOWNGRADE

Affected: 1.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.1

1. Check installed version

apt-cache policy wheatblog || rpm -q wheatblog || wheatblog --version

2. No fixed release: DOWNGRADE to a release before 1.1 (Debian / Ubuntu)

apt-cache madison wheatblog sudo apt install wheatblog=<VERSION_BEFORE_1.1> sudo apt-mark hold wheatblog

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list wheatblog sudo dnf downgrade wheatblog-<VERSION_BEFORE_1.1> sudo dnf versionlock add wheatblog

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2006-7002?

wheatblog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2006-7002 being exploited?

CVE-2006-7002 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2006-7002 affect?

CVE-2006-7002 affects wheatblog. Severity is medium (CVSS 4.3). Cross-site scripting (XSS) vulnerability in add_comment.php in Wheatblog (wB) 1.1 allows remote attackers to inject arbitrary web script or HTML via the Email field. NOTE: the provenance of this information is unknown; the details are obta

How urgent is CVE-2006-7002?

Priority 35/100. Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2007-3557 MEDIUM 6.8 DOWNGRADE SQL injection vulnerability in admin/login.php in Wheatblog (wB) 1.1, when magic_quotes_gpc is disabled, allow
CVE-2006-5922 MEDIUM 5.0 UPGRADE index.php in Wheatblog (wB) allows remote attackers to obtain sensitive information via certain values of the
CVE-2006-5921 MEDIUM 5.8 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in add_comment.php in Wheatblog (wB) allow remote attacker
CVE-2006-5195 MEDIUM 6.8 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in Wheatblog 1.0 and 1.1 allow remote attackers to inject
CVE-2006-4198 MEDIUM 5.1 UPGRADE PHP remote file inclusion vulnerability in includes/session.php in Wheatblog (wB) 1.1 and earlier, when regist

References

← Back to latest CVEs