CVE-2022-42991: A stored cross-site scripting (XSS) vulnerability in Simple Online Public Access Catalog v1.0 allows attack...
A stored cross-site scripting (XSS) vulnerability in Simple Online Public Access Catalog v1.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Edit Account Full Name field.
Security readout for executives and security teams
Plain-English summary
This is a stored cross-site scripting issue in Simple Online Public Access Catalog v1.0. An authenticated attacker can place malicious HTML or script into the Edit Account Full Name field, which may later run in another user’s browser. Business impact is mainly account/session risk and content tampering, not direct server takeover.
Executive priority
Treat as a moderate-priority web application issue. It is less urgent than unauthenticated remote code execution, but it can support account abuse or phishing inside the application and should be fixed during the next security maintenance window.
Technical view
CVE-2022-42991 is CWE-79 stored XSS with CVSS 3.1 score 5.4. The vector indicates network access, low complexity, low privileges required, user interaction required, changed scope, and low confidentiality and integrity impact. The vulnerable input is the Edit Account Full Name field in Simple Online Public Access Catalog v1.0.
Likely exposure
Exposure is limited to deployments of Simple Online Public Access Catalog v1.0, especially where users can edit account profile names. The CVE record does not provide vendor, product CPEs, or broader affected-version metadata, so inventory confirmation is necessary.
Exploitation context
The source bundle lists a public GitHub proof-of-concept reference, but it does not establish active exploitation. The CVE is not listed as KEV in the provided data. Exploitation requires authenticated access and another user viewing the stored content.
Researcher notes
Evidence is sparse: the CVE description identifies the field and version, and the CVSS vector defines constraints. A public PoC reference exists, but the provided sources do not name a patch, CPE, vendor advisory, or confirmed exploitation campaign.
Mitigation direction
Check project or vendor guidance for an official fix or replacement version.
Restrict account profile editing to trusted users until remediation is confirmed.
Sanitize and HTML-encode stored profile fields before rendering them.
Consider disabling the vulnerable application if it is unsupported or internet-facing.
Review CSP and session protections to reduce browser-side impact.
Validation and detection
Inventory systems for Simple Online Public Access Catalog v1.0.
Confirm whether the Edit Account Full Name field stores and renders untrusted markup.
Review application logs for unusual account name changes.
Check whether any vendor or project advisory names a patched version.
Verify that rendered profile data is encoded after remediation.
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.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.