← WordPress Vulnerabilities
WordPress security by component

Contests by Rewards Fuel

Contests by Rewards Fuel is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Dec 18, 2024; the highest published CVSS base score is 6.4.

Plugin slug: contests-by-rewards-fuel

CVE-2024-12513: Contests by Rewards Fuel: Cross-site scripting

Contests by Rewards Fuel is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.

PublishedDec 18, 2024
Safe version guidanceSee mitigation notes
Published vulnerabilities for contests-by-rewards-fuel
Safe version
Dec 18, 2024 CVE-2024-12513
Contests by Rewards Fuel: Cross-site scripting
Contests by Rewards Fuel is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE6.4
NVDPending
Mar 20, 2024 CVE-2024-1787
Contests by Rewards Fuel: Cross-site scripting
Contests by Rewards Fuel is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVDPending
Mar 20, 2024 CVE-2024-1785
Contests by Rewards Fuel: Cross-site request forgery
Contests by Rewards Fuel is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
See mitigation notes
CVE5.4
NVDPending