Security readout for executives and security teams
Plain-English summary
CVE-2022-36530 is a reported cross-site scripting issue in rageframe2 2.6.37 involving user-agent related parameters on info.php. The public record does not provide a CVSS score, affected CPEs, confirmed patch, or evidence of active exploitation.
Executive priority
Prioritize identification over emergency response. The issue could affect browser users if exposed, but public evidence is too limited to justify a higher urgency rating without local exposure confirmation.
Technical view
The CVE describes XSS in the info.php page of rageframe2 2.6.37, tied to user-agent related parameters. Available source data is sparse and does not document exploit maturity, exact impact scope, authentication requirements, or fixed versions.
Likely exposure
Exposure is most likely limited to deployments running rageframe2 2.6.37 where info.php exists and is reachable by users or the internet.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle. The sources do not establish active exploitation or provide reliable exploit status.
Researcher notes
The record lacks CVSS, CWE, affected CPEs, and fixed-version details. Treat the GitHub issue as the primary technical reference, but avoid assuming exploitability details beyond XSS in info.php user-agent related parameters.
Mitigation direction
- Inventory rageframe2 deployments and confirm whether version 2.6.37 is in use.
- Check the upstream repository and issue for maintainer guidance or fixed releases.
- Restrict access to info.php unless it is required for operations.
- Apply normal XSS defenses through validated vendor updates or reviewed code changes.
Validation and detection
- Confirm whether info.php is present and reachable in each deployment.
- Verify the installed rageframe2 version against application files or package metadata.
- Review logs for unusual requests to info.php and user-agent related input.
- Track the GitHub issue and CVE record for remediation updates.
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-2022-36530 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.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jianyan74/rageframe2CVE reference, mitre
- https://github.com/jianyan74/rageframe2/issues/106CVE reference, mitre
- https://github.com/jianyan74/rageframe2/issues/106?by=xboy%28Topsec%29CVE reference, mitre
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.