What is the severity of CVE-2007-6546?

The severity of CVE-2007-6546 is considered important due to the risk of session hijacking.

How do I fix CVE-2007-6546?

To fix CVE-2007-6546, update to RunCMS version 1.6.1 or later, where the predictable session ID vulnerability is resolved.

What is the impact of CVE-2007-6546?

The impact of CVE-2007-6546 includes the potential for remote attackers to hijack user sessions.

Which versions of RunCMS are affected by CVE-2007-6546?

RunCMS versions before 1.6.1 are affected by CVE-2007-6546, particularly versions up to 1.6.

Who is at risk from CVE-2007-6546?

Users of RunCMS prior to version 1.6.1 are at risk from CVE-2007-6546 due to session management vulnerabilities.

Vulnerability/
CVE-2007-6546

medium

6.4

CWE

NVD-CWE-Other

28/12/2007

7/8/2024

CVE-2007-6546

First published: Fri Dec 28 2007(Updated: )

RunCMS before 1.6.1 uses a predictable session id, which makes it easier for remote attackers to hijack sessions via a modified id.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Runcms Runcms	<=1.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-6546?
The severity of CVE-2007-6546 is considered important due to the risk of session hijacking.
How do I fix CVE-2007-6546?
To fix CVE-2007-6546, update to RunCMS version 1.6.1 or later, where the predictable session ID vulnerability is resolved.
What is the impact of CVE-2007-6546?
The impact of CVE-2007-6546 includes the potential for remote attackers to hijack user sessions.
Which versions of RunCMS are affected by CVE-2007-6546?
RunCMS versions before 1.6.1 are affected by CVE-2007-6546, particularly versions up to 1.6.
Who is at risk from CVE-2007-6546?
Users of RunCMS prior to version 1.6.1 are at risk from CVE-2007-6546 due to session management vulnerabilities.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/last-modified-date
agent/author
agent/severity
agent/tags
agent/first-publish-date
agent/event
agent/description
agent/source
vendor/runcms
canonical/runcms runcms
version/runcms runcms/1.6

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2007-6546?
The severity of CVE-2007-6546 is considered important due to the risk of session hijacking.
How do I fix CVE-2007-6546?
To fix CVE-2007-6546, update to RunCMS version 1.6.1 or later, where the predictable session ID vulnerability is resolved.
What is the impact of CVE-2007-6546?
The impact of CVE-2007-6546 includes the potential for remote attackers to hijack user sessions.
Which versions of RunCMS are affected by CVE-2007-6546?
RunCMS versions before 1.6.1 are affected by CVE-2007-6546, particularly versions up to 1.6.
Who is at risk from CVE-2007-6546?
Users of RunCMS prior to version 1.6.1 are at risk from CVE-2007-6546 due to session management vulnerabilities.