🛡️ Sentinel: [CRITICAL] Fix hardcoded secret bypass in Nginx

[Snider]

🚨 Severity: CRITICAL
💡 Vulnerability: A hardcoded token ($arg_token = "xrpc-9f8e7d6c5b4a") was used as an authentication mechanism directly inside the Nginx configuration file (wordpress.conf) to bypass the block on the /xmlrpc.php endpoint. This exposes a static secret in version control that grants access to a known high-risk WordPress endpoint.
🎯 Impact: An attacker who discovers this hardcoded secret in the configuration repository can bypass intended access controls to the /xmlrpc.php endpoint, which is frequently used for brute-force attacks against WordPress. Furthermore, the practice of hardcoding secrets bypasses intended runtime environment variable injection.
🔧 Fix: Replaced the conditional bypass logic with an unconditional deny all; block for the /xmlrpc.php endpoint.
✅ Verification: Verified the syntax correctness using nginx -t and confirmed the hardcoded secret was removed. Documented the learning in .jules/sentinel.md.

---

PR created automatically by Jules for task 2772420941354489501 started by @Snider

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.