Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2011-10006

GamerZ WP-PostRatings wp-postratings.php cross site scripting

Low3.5EPSS 0.43%
Published
Updated
Reserved
Assigned by
VulDB

Description

A vulnerability was found in GamerZ WP-PostRatings up to 1.64. It has been classified as problematic. This affects an unknown part of the file wp-postratings.php. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. Upgrading to version 1.65 is able to address this issue. The identifier of the patch is 6182a5682b12369ced0becd3b505439ce2eb8132. It is recommended to upgrade the affected component. The identifier VDB-259629 was assigned to this vulnerability.

Scores

CVSS scores of CVE-2011-10006, by who scored it
Scored byCVSSScoreVector
VulDBCNA (assigner)3.1Low3.5CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
VulDBCNA (assigner)3.0Low3.5CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
VulDBCNA (assigner)2.0Medium4.0AV:N/AC:L/Au:S/C:N/I:P/A:N
NVDNVD · Analyzed3.1Medium6.1CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS (exploitation in 30 days)
0.43% · top 62% of all CVEs (4 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.5.

Weakness

Affected products

  • GamerZ · WP-PostRatings

    • affected 1.0
    • affected 1.1
    • affected 1.2
    • affected 1.3
    • affected 1.4
    • affected 1.5
    • affected 1.6
    • affected 1.7
    • affected 1.8
    • affected 1.9
    • affected 1.10
    • affected 1.11
    • affected 1.12
    • affected 1.13
    • affected 1.14
    • affected 1.15
    • affected 1.16
    • affected 1.17
    • affected 1.18
    • affected 1.19
    • affected 1.20
    • affected 1.21
    • affected 1.22
    • affected 1.23
    • affected 1.24
    • affected 1.25
    • affected 1.26
    • affected 1.27
    • affected 1.28
    • affected 1.29
    • affected 1.30
    • affected 1.31
    • affected 1.32
    • affected 1.33
    • affected 1.34
    • affected 1.35
    • affected 1.36
    • affected 1.37
    • affected 1.38
    • affected 1.39
    • and 25 more

References (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2011-10006 badge
[![CVE-2011-10006](https://trackcve.app/badge/CVE-2011-10006.svg)](https://trackcve.app/cve/CVE-2011-10006)

Record last updated .