CVE-2007-5597

N/A
Published: October 19, 2007 at 11:00 PM UTC
Updated: June 16, 2026 at 10:46 PM UTC
1 product affected across 1 vendorDrupal

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 1%

Description

The hook_comments API in Drupal 4.7.x before 4.7.8 and 5.x before 5.3 does not pass publication status, which might allow attackers to bypass access restrictions and trigger e-mail with unpublished comments from some modules, as demonstrated by (1) Organic groups and (2) Subscriptions.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.7.0 ≤ v < 4.7.85.0 ≤ v < 5.3
Affected range stops below 4.7.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (7)

x_refsource_CONFIRMVendor Advisory
http://drupal.org/node/184354
Third Party Advisoryx_refsource_SECUNIA
http://secunia.com/advisories/27292
Third Party Advisoryx_refsource_SECUNIA
http://secunia.com/advisories/27352
VDB Entryx_refsource_BIDThird Party Advisory
http://www.securityfocus.com/bid/26119
VDB Entryx_refsource_VUPENThird Party Advisory
http://www.vupen.com/english/advisories/2007/3546
VDB Entryx_refsource_XFThird Party Advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/37296

CVSS

Confidentiality
NONE
Integrity
PARTIAL
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-264

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card