CVE-2007-2546
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSession fixation vulnerability in Simple Machines Forum (SMF) 1.1.2 and earlier allows remote attackers to hijack web sessions by setting the PHPSESSID parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSession fixation vulnerability in Simple Machines Forum (SMF) 1.1.2 and earlier allows remote attackers to set the PHPSESSID cookie value before victim authentication, enabling session hijacking once the victim logs in.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SMF versionAccess the admin control panel or check the version number displayed in the forum footer, or look for a version file in the SMF installation directoryAffected if The installed version is 1.1.2 or any earlier version (1.1.1, 1.1.0, etc.)
-
Check PHP session configurationCreate a PHPinfo page or check the php.ini file for session.cookie_httponly settings and verify how PHPSESSID cookies are handledAffected if PHPSESSID cookies can be set or controlled by external sources before authentication
-
Verify session ID regeneration on loginInspect the SMF source code (typically in LogIn.php or similar) to see if session_regenerate_id(true) is called after successful user authenticationAffected if Session IDs are NOT regenerated upon user login - the same PHPSESSID persists before and after authentication
-
Test session fixation vulnerabilitySet a known PHPSESSID value via cookie before logging in, then authenticate as a user and verify whether the same session ID is still activeAffected if The attacker-controlled PHPSESSID remains active after the victim logs in, allowing session hijacking
You are affected if SMF version is 1.1.2 or earlier AND session IDs are not regenerated upon user login, allowing an attacker to pre-set the PHPSESSID and hijack authenticated sessions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRegenerate session IDs upon user login using session_regenerate_id(true) and implement proper session validation to prevent attacker-controlled session fixation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2546 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-2546 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data