SECURITYCRITICALCVE-2026-78477

WordPress Jawn Theme Unauthenticated Privilege Escalation

CVE-2026-78477 allows unauthenticated attackers to escalate to WordPress administrator in Jawn theme versions up to 1.4.2, CVSS 9.8 critical.

Dylan H.

Security Team

August 25, 2026
5 min read
WordPress Jawn Theme Unauthenticated Privilege Escalation

Critical severity

Rated critical. Prioritise patching — see the remediation guidance below.

Affected Products

  • WordPress Jawn Theme <= 1.4.2

Executive Summary

CVE-2026-78477 is a critical privilege escalation vulnerability (CVSS 9.8) in the Jawn theme for WordPress, affecting all versions up to and including 1.4.2. An unauthenticated attacker can exploit this flaw to elevate their privileges to that of a WordPress administrator — gaining full control of the affected site without any prior credentials.

AttributeValue
CVE IDCVE-2026-78477
CVSS Score9.8 (Critical)
TypePrivilege Escalation (Authentication Bypass)
Attack VectorNetwork
AuthenticationNone required
User InteractionNone
Affected VersionsJawn Theme ≤ 1.4.2
Published2026-08-25

Vulnerability Details

The Jawn WordPress theme contains a flaw in its user registration or role assignment logic that allows an unauthenticated attacker to obtain administrator-level access. WordPress privilege escalation vulnerabilities of this class typically stem from one of the following root causes:

  • Insecure user registration endpoint — A theme-provided AJAX action or REST endpoint allows arbitrary role assignment during user creation
  • Missing capability checks — Administrative functions lack current_user_can() or nonce verification, allowing unauthenticated invocation
  • Exposed privileged action hooks — Theme hooks registered without authentication guards that can be triggered by unauthenticated HTTP requests

The impact is complete: a successful exploit yields full WordPress admin access, enabling the attacker to install plugins, modify site content, create backdoor accounts, and execute server-side code through the theme/plugin editor.


Affected Versions

ProductAffectedFixed
WordPress Jawn ThemeAll versions ≤ 1.4.21.4.3+ (if available)

Sites running Jawn theme versions 1.4.2 and earlier are vulnerable. There is no indication that older or newer versions are exempt unless a specific patch has been released.


Impact

A successful exploit allows an unauthenticated remote attacker to:

  1. Gain full WordPress administrator access with no credentials
  2. Install malicious plugins — delivering webshells, skimmers, or backdoors
  3. Deface or alter site content — for phishing, misinformation, or SEO spam
  4. Create persistent backdoor accounts — surviving theme updates
  5. Execute PHP code — via the built-in theme/plugin editor if not disabled
  6. Exfiltrate the WordPress database — including all user credentials, private content, and personal data
  7. Pivot to the underlying server — if file write permissions and PHP execution are available

Risk Context

WordPress powers approximately 40% of the web. Theme-based privilege escalation vulnerabilities are a preferred initial access vector for threat actors deploying credit card skimmers (Magecart), SEO spam injectors, and ransomware droppers. A CVSS 9.8 rating reflects the near-zero exploitation barrier: no credentials, no user interaction, fully remote.


Remediation

Immediate Actions

  1. Update Jawn theme immediately — Apply the patched version (1.4.3 or later) as soon as it is available from the theme developer or the WordPress theme directory.

  2. If no patch is available — deactivate the theme — Switch to a default WordPress theme (Twenty Twenty-Four, etc.) until a fix is released. A vulnerable active theme is a critical exposure.

  3. Audit for compromise — Check for:

    • Newly created administrator accounts not created by site owners
    • Unexpected plugin installations
    • Modified theme or plugin files (checksums via WP-CLI: wp plugin verify-checksums --all)
    • Unfamiliar scheduled cron jobs
  4. Restrict registration — If user registration is not required, disable it in WordPress Settings → General → "Anyone can register."

  5. Implement a WAF — Web Application Firewalls (Wordfence, Cloudflare WAF) can block exploitation attempts while patching is underway.

WP-CLI Audit Commands

# List all administrator accounts
wp user list --role=administrator
 
# Verify plugin file integrity
wp plugin verify-checksums --all
 
# Check recently modified files
find /var/www/html/wp-content -name "*.php" -newer /var/www/html/wp-config.php
 
# List all active plugins
wp plugin list --status=active

Detection

Indicators of Compromise

IndicatorDescription
Unexpected admin user accountsAttacker created backdoor admin
POST requests to /wp-admin/admin-ajax.php with action=jawn_* from unauthenticated sourcesExploit attempt
New plugin installations without admin activityPost-exploit persistence
Modified functions.php or theme filesWebshell or backdoor injection
Cron jobs calling external URLsMalware beacon or C2

Log Review

# Check Apache/Nginx logs for suspicious POST requests
grep -i "admin-ajax\|wp-json.*jawn\|register" /var/log/nginx/access.log | grep "POST" | grep " 200 "
 
# Check for new admin users created recently
wp user list --role=administrator --format=table

Key Takeaways

  1. CVSS 9.8 Critical — Unauthenticated privilege escalation to WordPress admin
  2. Zero barriers to exploit — No credentials, no interaction, fully remote
  3. Deactivate immediately if no patch — An unpatched active theme is an open door
  4. Audit for compromise — The vulnerability may already be exploited; check for new admin accounts and modified files
  5. Apply defense-in-depth — WAF, least-privilege file permissions, and registration restrictions reduce exposure while patching proceeds

References