# CVE-2025-43918: Business logic in SSL.com

> Attackers can obtain trusted TLS certificates for domains they do not control by exploiting a flaw in SSL.com's domain validation logic.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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:** 19 Apr 2025
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-6294-g9w5-7vm5

## What is CVE-2025-43918?

CVE-2025-43918 is a medium-severity vulnerability in SSL.com, published on 19 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SSL.com before 2025-04-19, when domain validation method 3.2.2.4.14 is used, processes certificate requests such that a trusted TLS certificate may be issued for the domain name of a requester's email address, even when the requester does not otherwise establish administrative control of that domain.

Weakness: CWE-348 (Use of Less Trusted Source)

## Which versions are affected by CVE-2025-43918?


## How do I fix CVE-2025-43918?

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

## Is CVE-2025-43918 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43918 and fix it if it is affected.

What it is: CVE-2025-43918 is a medium-severity vulnerability in SSL.com, published on 19 Apr 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-2025-43918 in the wild and no public exploit code.

Affected product: SSL.com. 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-2025-43918/ (Markdown: https://insights.sbomify.com/CVE-2025-43918/index.md)
```

## Sources

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

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