# praisonai-platform: list_issue_activity returns activity log for any issue regardless of workspace ownership

Advisory record · `GHSA-27p4-pjqv-whgj`

- **Identifiers:** `GHSA-27p4-pjqv-whgj` · `CVE-2026-47408` · `PYSEC-2026-2927`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 29 May 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 May 2026, 22:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `praisonai-platform` (PyPI): affected `<0.1.4`; fixed in `0.1.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of praisonai-platform before 0.1.4 let any user who is a member of one workspace read the full activity log of an issue belonging to a different workspace, because the issue-scoped activity endpoint checks membership of the URL's workspace but does not confirm the issue belongs to it. An attacker needs only a workspace-member account and the target issue's ID, and could then see who acted on the issue, what changed, and the before-and-after values recorded in the activity details. Upgrade to praisonai-platform 0.1.4 or later, which fixes the issue.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 22nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-27p4-pjqv-whgj)

## Sources

- [GitHub Advisory Database: GHSA-27p4-pjqv-whgj](https://github.com/advisories/GHSA-27p4-pjqv-whgj)
- [OSV: GHSA-27p4-pjqv-whgj](https://osv.dev/vulnerability/GHSA-27p4-pjqv-whgj)
- <https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-27p4-pjqv-whgj>
- <https://github.com/MervinPraison/PraisonAI>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-27p4-pjqv-whgj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-27p4-pjqv-whgj/>. Everything for agents: <https://agentprime.io/llms.txt>.
