# GHSA-pm52-wwrw-c282: Command Injection in wiki-plugin-datalog

> Attackers can inject commands via unsanitized URLs in the curl endpoint, potentially achieving remote code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2019

## What is GHSA-pm52-wwrw-c282?

GHSA-pm52-wwrw-c282 is a command injection vulnerability in wiki-plugin-datalog, published on 13 Jun 2019. It can be exploited over the network, with no action from the victim.

### Official description

Versions of `wiki-plugin-datalog` prior to 0.1.6 are vulnerable to Command Injection. The package failed to sanitize URLs on the curl endpoint, allowing attackers to inject commands and possibly achieving Remote Code Execution on the system.

## Recommendation

Upgrade to version 0.1.6 or later.

## Which versions are affected by GHSA-pm52-wwrw-c282?

2 open source packages ship an affected version, including wiki-plugin-datalog.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wiki-plugin-datalog` | npm | All versions | 0.1.6 |
| `wiki-plugin-datalog` | npm | All versions | 0.1.6 |

## How do I fix GHSA-pm52-wwrw-c282?

Upgrade wiki-plugin-datalog to 0.1.6 or later.

## Is GHSA-pm52-wwrw-c282 being exploited?

There is no known exploitation of GHSA-pm52-wwrw-c282 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-pm52-wwrw-c282 and fix it if it is affected.

What it is: GHSA-pm52-wwrw-c282 is a command injection vulnerability in wiki-plugin-datalog, published on 13 Jun 2019. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-pm52-wwrw-c282 in the wild and no public exploit code.

Affected packages and fixed versions:
- wiki-plugin-datalog (npm): affected all versions; fixed in 0.1.6
- wiki-plugin-datalog (npm): affected all versions; fixed in 0.1.6

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/GHSA-pm52-wwrw-c282/ (Markdown: https://insights.sbomify.com/GHSA-pm52-wwrw-c282/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-pm52-wwrw-c282

---
From sbomify Insights: https://insights.sbomify.com/GHSA-pm52-wwrw-c282/
Summaries are generated and may contain mistakes; the official description above is the record.