LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0624: OrangeScrum version 2.0.11 allows an external attacker to obtain arbitrary user accounts from the application.

OrangeScrum version 2.0.11 allows an external attacker to obtain arbitrary user accounts from the application. This is possible because the application returns malicious user input in the response with the content-type set to text/html.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

OrangeScrum 2.0.11 can reflect attacker-controlled input as HTML, creating a cross-site scripting risk. A victim must interact with malicious content, but the attacker does not need an account. Successful exploitation could expose user account information or allow limited actions in the victim’s browser context.

Executive priority

Treat this as a medium-priority web application issue. It is not confirmed as actively exploited, but internet-facing OrangeScrum 2.0.11 systems should be remediated promptly because account exposure is possible after user interaction.

Technical view

CVE-2023-0624 is a CWE-79 issue in OrangeScrum 2.0.11. The application returns malicious user input in a response served as text/html. CVSS 3.1 is 6.1 with network attack vector, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to organizations running OrangeScrum version 2.0.11, especially if the application is internet-facing or reachable by untrusted users. The source bundle does not identify other affected versions or products.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not claim active exploitation. Exploitation requires user interaction, consistent with reflected cross-site scripting rather than automatic compromise.

Researcher notes

The record describes reflected input returned as HTML and maps to CWE-79. Evidence is incomplete on exact endpoints, patch version, and vendor remediation status, so avoid broad version claims beyond OrangeScrum 2.0.11.

Mitigation direction

  • Identify any OrangeScrum 2.0.11 deployments in production, staging, and exposed test environments.
  • Check OrangeScrum and Fluid Attacks guidance for an official fix or vendor-approved workaround.
  • Reduce untrusted access to exposed OrangeScrum instances until remediation is confirmed.
  • Validate that reflected user input is encoded and not returned as executable HTML.
  • Use monitoring controls to detect suspicious reflected-script attempts against OrangeScrum endpoints.

Validation and detection

  • Confirm deployed OrangeScrum versions through asset inventory or application administration records.
  • Review affected responses for reflected user input served with text/html content type.
  • Check application, proxy, and WAF logs for suspicious input targeting OrangeScrum pages.
  • Verify remediation with regression tests covering reflected input and response content handling.
Prepared
Confidence
medium
Sources
4

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-0624 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
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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.

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

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2023-0624Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aOrangeScrum2.0.11Listed
Weakness

CWE details

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.