What is the severity of CVE-2005-1946?

CVE-2005-1946 is considered a high severity vulnerability due to the risk of arbitrary SQL command execution.

How do I fix CVE-2005-1946?

To fix CVE-2005-1946, upgrade Invision Blog to version 1.1.2 Final or later.

What software is affected by CVE-2005-1946?

CVE-2005-1946 affects Invision Blog versions 1.0 and 1.1 prior to 1.1.2 Final.

What can attackers achieve with CVE-2005-1946?

Attackers can execute arbitrary SQL commands on the database through multiple entry points.

Is CVE-2005-1946 still a risk today?

While it's an older vulnerability, systems running vulnerable versions of Invision Blog without updates may still be at risk.

Vulnerability/
CVE-2005-1946

high

7.5

CWE

NVD-CWE-Other 89

9/6/2005

14/6/2005

7/8/2024

CVE-2005-1946: SQL Injection

First published: Thu Jun 09 2005(Updated: )

Multiple SQL injection vulnerabilities in Invision Blog before 1.1.2 Final allow remote attackers to execute arbitrary SQL commands via the (1) eid parameter to an editentry, replyentry, or editcomment action, or (2) the mid parameter to an aboutme action.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Invision Community	=1.1
Invision Community	=1.0

Remedy

http://www.gulftech.org/?node=research&article_id=00078-06072005

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-1946?
CVE-2005-1946 is considered a high severity vulnerability due to the risk of arbitrary SQL command execution.
How do I fix CVE-2005-1946?
To fix CVE-2005-1946, upgrade Invision Blog to version 1.1.2 Final or later.
What software is affected by CVE-2005-1946?
CVE-2005-1946 affects Invision Blog versions 1.0 and 1.1 prior to 1.1.2 Final.
What can attackers achieve with CVE-2005-1946?
Attackers can execute arbitrary SQL commands on the database through multiple entry points.
Is CVE-2005-1946 still a risk today?
While it's an older vulnerability, systems running vulnerable versions of Invision Blog without updates may still be at risk.

agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/references
agent/weakness
agent/last-modified-date
agent/severity
agent/remedy
agent/description
agent/event
agent/source
agent/tags
collector/nvd-historical
vendor/invision power services
product/invision community blog
canonical/invision power services invision community blog
agent/software-canonical-lookup-request
collector/nvd-index
canonical/invision community
version/invision community/1.1
version/invision community/1.0

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-2005-1946?
CVE-2005-1946 is considered a high severity vulnerability due to the risk of arbitrary SQL command execution.
How do I fix CVE-2005-1946?
To fix CVE-2005-1946, upgrade Invision Blog to version 1.1.2 Final or later.
What software is affected by CVE-2005-1946?
CVE-2005-1946 affects Invision Blog versions 1.0 and 1.1 prior to 1.1.2 Final.
What can attackers achieve with CVE-2005-1946?
Attackers can execute arbitrary SQL commands on the database through multiple entry points.
Is CVE-2005-1946 still a risk today?
While it's an older vulnerability, systems running vulnerable versions of Invision Blog without updates may still be at risk.