WordPress / WordPress/wordpress.org
Plugin Directory: Enforce owner-domain verification for Plugin URI / Author URI on new plugin submissions
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 163
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
Summary
We currently show ownership guidance in the upload UI, but we do not enforce it during submission checks.
For new plugin submissions, we should validate plugin header URLs (Plugin URI, Author URI) against the submitter’s verified email domain (or require a clear ownership proof flow).
Problem
At submit time, plugin metadata can claim organization/project ownership without domain alignment, which can mislead users and reviewers.
Proposal
Add a new validation step in submission flow (shortcodes/class-upload-handler.php) for new submissions:
- Parse domains from:
Plugin URIAuthor URI
- Compare those domains to the submitter’s email domain (from profile email).
- If domain does not match and no approved ownership proof exists, block submission with actionable error text.
Error message (proposed)
Error: Ownership could not be verified for plugin URLs.
The domain used in Plugin URI/Author URI must match your profile email domain, or you must provide ownership verification. Update your profile email domain or contact plugins@wordpress.org with proof of ownership.
Scope
- Apply on new plugin submissions.
- Do not block existing plugins updating versions (unless we explicitly decide to extend later).
- Keep current “Plugin URI and Author URI must be different” rule.
Acceptance criteria
- New submission fails when
Plugin URI/Author URIdomain does not match submitter email domain and no override/proof exists. - New submission succeeds when domain matches.
- New submission succeeds when approved ownership proof/override exists.
- Clear reviewer-facing logging for failures/overrides.
Notes
Related UI copy already exists in shortcodes/class-upload.php under “Plugin Ownership”, but backend enforcement is missing.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in shortcodes/class-upload-handler.php and compare the existing ownership guidance in shortcodes/class-upload.php. Trace the new-submission checks and profile email data, then define how approved ownership proof or overrides are represented and logged. Done means mismatched domains are blocked with actionable errors, matching domains and approved overrides pass, and existing plugin updates remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100