Security readout for executives and security teams
Plain-English summary
CVE-2020-25352 is a stored cross-site scripting issue in rConfig 3.9.5. An attacker could save crafted content in a device Model field, causing JavaScript to run when a user views the affected page. The source says it was fixed in version 3.9.6.
Executive priority
Prioritize remediation where rConfig is used by network administrators or exposed to broad internal access. This is not KEV-listed in the provided sources, but stored XSS in an infrastructure management tool can create meaningful operational risk.
Technical view
The flaw is in the /devices.php device handling path for rConfig 3.9.5. Unsanitized or improperly encoded Model field content could persist and later execute as JavaScript in another user's browser. The bundle provides no CVSS score, CWE, detailed affected CPEs, or exploit-in-the-wild evidence.
Likely exposure
Organizations are most exposed if they run rConfig 3.9.5 and allow users to create or edit device records. Exposure is higher where rConfig manages sensitive network infrastructure and administrative users regularly view device pages.
Exploitation context
The sources describe remote attacker capability to enter crafted content into the Model field and save it. They do not show active exploitation, KEV listing, or confirmed exploitation at scale. Treat exploitability details beyond that as incomplete.
Researcher notes
Evidence is limited to the CVE description and one public reference. The bundle names rConfig 3.9.5 and a fix in 3.9.6, but provides no CVSS vector, affected CPEs, authentication requirements, or patch advisory details.
Mitigation direction
- Upgrade rConfig 3.9.5 to version 3.9.6 or later.
- Restrict device edit permissions to trusted administrative users.
- Review vendor guidance before applying compensating controls.
- Audit stored device Model values for suspicious script-like content.
Validation and detection
- Inventory rConfig deployments and identify any 3.9.5 instances.
- Confirm the deployed version is 3.9.6 or later after remediation.
- Review who can create or edit device records.
- Check device Model field data for unexpected HTML or JavaScript-like content.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-25352 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://stark0de.com/2020/08/27/pwning-rconfig-part-one.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.