# CVE-2024-48572: Information disclosure in n/a

> Unauthenticated attackers can enumerate user email addresses in AquilaCMS via the Add a user feature due to insufficient input validation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-8798-5c83-39gj

## What is CVE-2024-48572?

CVE-2024-48572 is a medium-severity vulnerability in n/a, published on 29 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A User enumeration vulnerability in AquilaCMS 1.409.20 and prior allows unauthenticated attackers to obtain email addresses via the "Add a user" feature. The vulnerability occurs due to insufficiently validated user input being processed as a regular expression, which is then matched against email addresses to find duplicate entries.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Aquila-Cms Aquilacms.

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

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

## Is CVE-2024-48572 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-48573](https://insights.sbomify.com/CVE-2024-48573/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48572 is a medium-severity vulnerability in n/a, published on 29 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-48572 in the wild and no public exploit code.

Affected product: n/a. 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-48572/ (Markdown: https://insights.sbomify.com/CVE-2024-48572/index.md)
```

## Sources

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

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