How severe is CVE-2020-12259?

No CVSS score has been assigned to CVE-2020-12259 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2020-12259?

Affected package information for CVE-2020-12259 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-12259?

No fixed release is recorded for CVE-2020-12259 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2020-12259 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2020-12259 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2020-12259 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-12259 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-12259?

CVE-2020-12259 has an EPSS (Exploit Prediction Scoring System) score of 96.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2020-12259?

CVE-2020-12259 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2020-12259?

A Nuclei detection template exists for CVE-2020-12259, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-12259 published, and has it been updated?

CVE-2020-12259 was published on May 18, 2020 and was last updated on August 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2020-12259 — Farid007

CVE-2020-12259 is a Cross-site Scripting (XSS) vulnerability. EPSS puts its 30-day exploitation probability at 96.4% (100th percentile). No vendor fix is recorded yet; mitigation options are listed below.

rConfig 3.9.4 is vulnerable to reflected XSS. The configDevice.php file improperly validates user input. An attacker can exploit this vulnerability by crafting arbitrary JavaScript…

Published

May 18, 2020

Updated

Aug 4, 2024

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

96.4%probability of exploitation in next 30 days

Very High Risk+0.17%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

rConfig 3.9.4 is vulnerable to reflected XSS. The configDevice.php file improperly validates user input. An attacker can exploit this vulnerability by crafting arbitrary JavaScript in the rid GET parameter of devicemgmnt.php.

Affected Products

1 product · 1 configurations

Application

rconfigrconfig

1 version

3.9.4

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2020-12259 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

How to detect CVE-2020-12259

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2020-12259 -u https://target

Template: rConfig 3.9.4 - Cross-Site Scripting
Severity: medium
Impact: Authenticated attackers can inject malicious JavaScript through the rid parameter, potentially stealing session cookies or performing administrative actions on behalf of authenticated users.
Remediation: Upgrade to rConfig version 3.9.7 or later.

Template by ProjectDiscovery nuclei-templates (r3Y3r53), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-12259 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works