LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37392: In RPCMS v1.8 and below, the "nickname" variable is not properly sanitized before being displayed on page.

In RPCMS v1.8 and below, the "nickname" variable is not properly sanitized before being displayed on page. When the API functions are enabled, the attacker can use API to update user nickname with XSS payload and achieve stored XSS. Users who view the articles published by the injected user will trigger the XSS.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

RPCMS v1.8 and earlier can store unsafe script content in a user nickname when API functions are enabled. That nickname is later displayed to readers of that user’s articles, causing browser-side script execution. Business risk depends on whether RPCMS is deployed, APIs are enabled, and privileged users view affected content.

Executive priority

Treat this as a targeted web application hygiene issue, not an emergency unless RPCMS is internet-facing and API profile updates are enabled. Prioritize rapid inventory first, then configuration hardening and vendor guidance review.

Technical view

The source describes stored cross-site scripting caused by insufficient sanitization of the nickname field before rendering. An attacker able to update a nickname through enabled API functions can persist malicious content that executes when articles by that account are viewed. No CVSS score, CWE, patch version, or KEV listing is provided.

Likely exposure

Exposure is likely limited to organizations running RPCMS v1.8 or below with API functions enabled and user nickname updates reachable. The provided affected-product metadata is incomplete, so asset owners should verify RPCMS usage directly rather than relying on CPE matching.

Exploitation context

The CVE description supports stored XSS through nickname rendering. The source bundle includes a public gist reference, but no KEV listing and no cited evidence of active exploitation. Requirements appear to include API functions being enabled and a victim viewing articles by the modified user.

Researcher notes

The record is sparse: severity, CVSS, CWE, CPEs, and fixed-version details are absent. Analysis should stay anchored to RPCMS v1.8 and below, enabled API functions, nickname update capability, and article-view rendering. Avoid assuming broader RPCMS components are affected.

Mitigation direction

  • Identify any RPCMS deployments and confirm whether they are v1.8 or earlier.
  • Disable RPCMS API functions if they are not operationally required.
  • Check RPCMS project guidance for any fixed release or official mitigation.
  • Ensure nickname output is HTML-encoded wherever displayed.
  • Remove or neutralize suspicious existing nickname values in affected databases.
  • Restrict who can update user profile fields through APIs.

Validation and detection

  • Inventory public and internal sites for RPCMS usage and version evidence.
  • Review RPCMS configuration to determine whether API functions are enabled.
  • Confirm nickname fields are encoded before rendering on article pages.
  • Inspect stored nickname values for script-like or HTML-like content.
  • Review access logs for unusual profile update activity.
  • Document uncertainty where version or configuration cannot be confirmed.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2021-37392 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.