CVE-2012-10017: BestWebSoft Portfolio Plugin cross-site request forgery

Q: What is the severity of CVE-2012-10017?

CVE-2012-10017 has been classified as problematic due to its potential for cross-site request forgery.

Q: How do I fix CVE-2012-10017?

To fix CVE-2012-10017, upgrade the BestWebSoft Portfolio Plugin to version 2.06 or later.

Q: What type of vulnerability is CVE-2012-10017?

CVE-2012-10017 is a cross-site request forgery (CSRF) vulnerability.

Q: Which software is affected by CVE-2012-10017?

CVE-2012-10017 affects the BestWebSoft Portfolio Plugin versions up to 2.04 on WordPress.

Q: Can CVE-2012-10017 be exploited remotely?

Yes, CVE-2012-10017 can be exploited remotely, enabling unauthorized actions on behalf of a user.

Published Dec 26, 2023

Updated

A vulnerability was found in BestWebSoft Portfolio Plugin up to 2.04 on WordPress. It has been classified as problematic. This affects an unknown part. The manipulation leads to cross-site request forgery. It is possible to initiate the attack remotely. Upgrading to version 2.06 is able to address this issue. The patch is named 68af950330c3202a706f0ae9bbb52ceaa17dda9d. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-248955.

Affected Software

1 affected component

Bestwebsoft Portfolio Wordpress<2.06

Remediation

Patch Available

https://github.com/wp-plugins/portfolio/commit/68af950330c3202a706f0ae9bbb52ceaa17dda9d

Event History

Dec 26, 2023

CVE Published

10:00 AM

Data Sourced

10:00 AM

DescriptionSeverityWeakness

Data Sourced

via NVD·10:15 AM

RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

What is the severity of CVE-2012-10017?

CVE-2012-10017 has been classified as problematic due to its potential for cross-site request forgery.

How do I fix CVE-2012-10017?

To fix CVE-2012-10017, upgrade the BestWebSoft Portfolio Plugin to version 2.06 or later.

What type of vulnerability is CVE-2012-10017?