Skip to content

🔒 Fix Stored XSS via REST API Meta Updates#14

Open
google-labs-jules[bot] wants to merge 1 commit intomainfrom
jules-7526099933523002537-946c023d
Open

🔒 Fix Stored XSS via REST API Meta Updates#14
google-labs-jules[bot] wants to merge 1 commit intomainfrom
jules-7526099933523002537-946c023d

Conversation

@google-labs-jules
Copy link

🎯 What: The update_callback for excerpt and seo_meta_desc fields in antigravity_cors.php allowed direct metadata manipulation without authorization checks or sanitization.
⚠️ Risk: Unauthenticated/unauthorized users or malicious actors could exploit this by making REST API requests with crafted $values, allowing Stored XSS injection into the site's meta descriptions or excerpts.
🛡️ Solution: Added a current_user_can('edit_post', $post->ID) authorization check to both callbacks, and wrapped the incoming $value with sanitize_textarea_field() prior to database insertion.


PR created automatically by Jules for task 7526099933523002537 started by @instituto-ops

🎯 **What:** The `update_callback` for `excerpt` and `seo_meta_desc` fields in `antigravity_cors.php` allowed direct metadata manipulation without authorization checks or sanitization.
⚠️ **Risk:** Unauthenticated/unauthorized users or malicious actors could exploit this by making REST API requests with crafted `$value`s, allowing Stored XSS injection into the site's meta descriptions or excerpts.
🛡️ **Solution:** Added a `current_user_can('edit_post', $post->ID)` authorization check to both callbacks, and wrapped the incoming `$value` with `sanitize_textarea_field()` prior to database insertion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants