LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0454: OrangeScrum version 2.0.11 allows an authenticated external attacker to delete arbitrary local files from t...

OrangeScrum version 2.0.11 allows an authenticated external attacker to delete arbitrary local files from the server. This is possible because the application uses an unsanitized attacker-controlled parameter to construct an internal path.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OrangeScrum 2.0.11 has a high-severity flaw that lets a logged-in remote attacker delete local server files. The issue can disrupt service and damage application or system data because attacker-controlled input is used in a file path without proper sanitization.

Executive priority

Prioritize remediation for any exposed OrangeScrum 2.0.11 system because the flaw can directly delete server files after login. Business impact is most likely service outage, data loss, or costly restoration work rather than data theft based on the CVSS vector.

Technical view

CVE-2023-0454 is a CWE-22 path traversal issue in OrangeScrum 2.0.11. An authenticated network attacker with low privileges can influence an internal path parameter and delete arbitrary local files. CVSS 3.1 is 8.1, with high integrity and availability impact and no confidentiality impact stated.

Likely exposure

Exposure is limited to OrangeScrum version 2.0.11 based on the provided sources. Risk is higher for internet-facing, partner-facing, or broadly accessible deployments where untrusted authenticated users can reach the affected functionality.

Exploitation context

The CVE record does not indicate CISA KEV listing, and the supplied sources do not state active exploitation. Treat this as plausible to exploit by authenticated users, but do not claim known exploitation from the provided evidence.

Researcher notes

The key evidence supports authenticated remote arbitrary local file deletion through unsanitized path construction. The source bundle does not provide a named fixed release, patch commit, endpoint details, or proof of active exploitation, so validation should stay non-destructive and vendor-guided.

Mitigation direction

  • Identify any OrangeScrum 2.0.11 deployments immediately.
  • Check OrangeScrum and Fluid Attacks guidance for fixed versions or workarounds.
  • Restrict OrangeScrum access to trusted networks and users.
  • Apply least-privilege filesystem permissions to the web server account.
  • Confirm recent, restorable backups for application and server files.

Validation and detection

  • Inventory OrangeScrum versions across production, staging, and legacy hosts.
  • Confirm whether untrusted authenticated users can access affected instances.
  • Review application and system logs for unusual file deletion activity.
  • Verify vendor remediation guidance before marking the issue fixed.
  • Retest after remediation without using destructive validation.
Prepared
Confidence
high
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-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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-0454 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
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

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

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
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2023-0454Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.