Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2012-10017: A vulnerability was found in BestWebSoft Portfolio Plugin up to 2.04 on WordPress

22
Routine
MEDIUM 4.3UPGRADE

CVE-2012-10017 is a medium-severity flaw (CVSS 4.3) affecting portfolio. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.4% (top 71%)
CISA exploited listNo
WeaknessCWE-352
Published2023-12-26
Last modified2026-06-16
Publisher (CNA): VulDB · Vendor: bestwebsoft

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

bestwebsoft portfolio UPGRADE
Affected: < 2.06
Fixed in: 2.06
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy portfolio || rpm -q portfolio || portfolio --version
2. UPGRADE to 2.06 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade portfolio
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade portfolio
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2012-10017?

portfolio: upgrade to 2.06. Exact commands for each OS are on this page.

Is CVE-2012-10017 being exploited?

CVE-2012-10017 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2012-10017 affect?

CVE-2012-10017 affects portfolio. Severity is medium (CVSS 4.3). 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 att

How urgent is CVE-2012-10017?

Priority 22/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.