# CVE-2025-48009: Single Content Sync - Moderately critical - Access bypass - SA-CONTRIB-2025-060

> Attackers can bypass authorization checks in the Single Content Sync module to misuse functionality without proper permissions.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/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:** Yes
- **Published:** 21 May 2025
- **Updated:** 21 May 2025
- **Also known as:** DRUPAL-CONTRIB-2025-060, GHSA-rxf3-624f-c767

## What is CVE-2025-48009?

CVE-2025-48009 is a low-severity missing authorization vulnerability in Drupal Single Content Sync, published on 21 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Drupal Single Content Sync allows Functionality Misuse.This issue affects Single Content Sync: from 0.0.0 before 1.4.12.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/single_content_sync` | Packagist:https://packages.drupal.org/8 | All versions | 1.4.12 |

Products: Single Content Sync Project Single Content Sync.

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

Upgrade to a fixed version.

## Is CVE-2025-48009 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48009 is a low-severity missing authorization vulnerability in Drupal Single Content Sync, published on 21 May 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-48009 in the wild and no public exploit code.

Affected product: Drupal Single Content Sync. 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-48009/ (Markdown: https://insights.sbomify.com/CVE-2025-48009/index.md)
```

## Sources

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

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