WordPress security changelog
MEDIUM CVE-2008-4616 Modified

SpamBam: A security weakness

SpamBam is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 5.0 CVSS · cve@mitre.org
NVD score 5.0 CVSS 2.0 · nvd@nist.gov
Component
SpamBam
Plugin slug
spambam-plugin
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Oct 20, 2008
Weakness
CWE-20 — Improper Input Validation

This CVE was published Oct 20, 2008 and is one of 1 known issue for this plugin.

What to do

Update, patch or deactivate.

Update SpamBam to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The SpamBam plugin for WordPress allows remote attackers to bypass restrictions and add blog comments by using server-supplied values to calculate a shared key.

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

References

Primary and upstream sources