# CVE-2024-30154: HCL SX is susceptible to a Cross-Site Request Forgery (CSRF) vulnerability

> An attacker can trick users into performing unauthorized actions in HCL SX, potentially leading to data modification or account takeover.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2025
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-rvh7-h8xh-g43v

## What is CVE-2024-30154?

CVE-2024-30154 is a medium-severity vulnerability in HCL SX, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCL SX is vulnerable to cross-site request forgery vulnerability which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-30154?

It affects 1 product.


Products: Hcltech Hcl Sx.

## How do I fix CVE-2024-30154?

No fix has been published for CVE-2024-30154 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-30154 being exploited?

There is no known exploitation of CVE-2024-30154 in the wild and no public exploit code.

## Other vulnerabilities in HCL SX

- [CVE-2024-30152](https://insights.sbomify.com/CVE-2024-30152/): HCL SX is affected by usage of a weak cryptographic algorithm (medium 6.5)
- [CVE-2024-30155](https://insights.sbomify.com/CVE-2024-30155/): HCL SX is susceptible to cookie with Insecure, Improper, or Missing SameSite attribute vulnerability (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30154 and fix it if it is affected.

What it is: CVE-2024-30154 is a medium-severity vulnerability in HCL SX, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-30154 in the wild and no public exploit code.

Affected product: HCL SX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-30154/ (Markdown: https://insights.sbomify.com/CVE-2024-30154/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-30154
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-30154
- OSV: https://osv.dev/vulnerability/CVE-2024-30154

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-30154/
Summaries are generated and may contain mistakes; the official description above is the record.