63f4a7c4da
Three duplicate/related reports, one mechanism: POST/PATCH handlers for work items, comments and issue links let a caller set created_by and created_at directly from the request body, even though the model already auto-populates created_by correctly on create (BaseModel.save() reads the authenticated user via crum). The escalation: forge created_by via PATCH on an existing issue, then pass IssueDetailAPIEndpoint.delete's "admin OR creator" gate as a plain project member — deleting arbitrary work items. Root cause had two independent halves: - Four view-level blocks (issue POST, issue PUT's external-id upsert create branch, comment POST, issue-link POST) re-fetched the row a serializer.save() had just correctly created — turning it into an UPDATE, where BaseModel.save()'s auto-created_by protection does not apply — then overwrote created_by/created_at straight from request.data. All four removed entirely; the initial serializer.save() already produces the right created_by unaided. - IssueSerializer never marked created_by read-only (unlike updated_by right beside it, and unlike created_at, which Django's auto_now_add protects independently). That let a plain PATCH on an *existing* issue set created_by directly via the serializer — this is what actually makes the delete-escalation chain possible, since PATCH never touched the view-level override blocks at all. Added to IssueSerializer.Meta.read_only_fields. Comment and issue-link PATCH already used properly-protected serializers (created_by already read-only, or absent from fields entirely) — their only gap was the POST-path override, now removed. Verified via fail-before: reverted the fix, 5 of 6 new tests correctly failed (forged attacker-controlled created_by landing in the DB); the 2 that passed regardless are intentional (a same-value no-op and a positive control). Confirmed IssueDetailAPIEndpoint.put has no route mounted anywhere (only ["get", "post"] on IssueListCreateAPIEndpoint) — cleaned up the same override there for consistency, but it's unreachable dead code, not a live vector. Tests: 6 new (apps/api/plane/tests/contract/api/test_created_by_forgery.py). Broader regression sweep (issue/comment/link/notification suites, 49 tests) green. ruff clean. Co-authored-by: Plane AI <noreply@plane.so>
Modern project management for all teams
Website • Forum • X • Documentation
Meet Plane, an open-source project management tool to track issues, run sprints cycles, and manage product roadmaps without the chaos of managing the tool itself. 🧘♀️
Plane is evolving every day. Your suggestions, ideas, and reported bugs help us immensely. Do not hesitate to join in the conversation on Forum or raise a GitHub issue. We read everything and respond to most.
🚀 Installation
Getting started with Plane is simple. Choose the setup that works best for you:
-
Plane Cloud Sign up for a free account on Plane Cloud—it's the fastest way to get up and running without worrying about infrastructure.
-
Self-host Plane Prefer full control over your data and infrastructure? Install and run Plane on your own servers. Follow our detailed deployment guides to get started.
| Installation methods | Docs link |
|---|---|
| Docker |  |
| Kubernetes |  |
Instance admins can configure instance settings with God mode.
🌟 Features
-
Work Items Efficiently create and manage tasks with a robust rich text editor that supports file uploads. Enhance organization and tracking by adding sub-properties and referencing related issues.
-
Cycles Maintain your team’s momentum with Cycles. Track progress effortlessly using burn-down charts and other insightful tools.
-
Modules Simplify complex projects by dividing them into smaller, manageable modules.
-
Views Customize your workflow by creating filters to display only the most relevant issues. Save and share these views with ease.
-
Pages Capture and organize ideas using Plane Pages, complete with AI capabilities and a rich text editor. Format text, insert images, add hyperlinks, or convert your notes into actionable items.
-
Analytics Access real-time insights across all your Plane data. Visualize trends, remove blockers, and keep your projects moving forward.
🛠️ Local development
See CONTRIBUTING
⚙️ Built with
📸 Screenshots
📝 Documentation
Explore Plane's product documentation and developer documentation to learn about features, setup, and usage.
❤️ Community
Join the Plane community on GitHub Discussions and our Forum. We follow a Code of conduct in all our community channels.
Feel free to ask questions, report bugs, participate in discussions, share ideas, request features, or showcase your projects. We’d love to hear from you!
🛡️ Security
If you discover a security vulnerability in Plane, please report it responsibly instead of opening a public issue. We take all legitimate reports seriously and will investigate them promptly. See Security policy for more info.
To disclose any security issues, please email us at security@plane.so.
🤝 Contributing
There are many ways you can contribute to Plane:
- Report bugs or submit feature requests.
- Review the documentation and submit pull requests to improve it—whether it's fixing typos or adding new content.
- Talk or write about Plane or any other ecosystem integration and let us know!
- Show your support by upvoting popular feature requests.
Please read CONTRIBUTING.md for details on the process for submitting pull requests to us.
Repo activity
We couldn't have done this without you.
License
This project is licensed under the GNU Affero General Public License v3.0.