Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker may gain WordPress administrator control on sites using the Jawn theme through version 1.4.2. Administrator access could enable content changes, data theft, account manipulation, malware placement, or service disruption. The supplied sources do not establish active exploitation or explain the underlying flaw.
Executive priority
Prioritize immediate inventory and containment. The reported flaw could permit complete site takeover without credentials or user action. Although active exploitation is not established, the potential business impact and low stated attack complexity justify urgent action on internet-facing installations.
Technical view
CVE-2026-78477 is classified as CWE-266 privilege escalation with CVSS 3.1 score 9.8. The vector indicates remote, low-complexity exploitation requiring neither authentication nor user interaction, with potentially high confidentiality, integrity, and availability impact. No vulnerable function, root cause, or confirmed fixed version is identified in the bundle.
Likely exposure
Potential exposure is limited to WordPress installations using Jawn version 1.4.2 or earlier. Publicly reachable sites present the clearest risk. Based on the supplied evidence, installations not using Jawn are not affected. The structured affected-version metadata conflicts with the narrative, so version scope should be verified with the vendor.
Exploitation context
The CVSS vector describes favorable exploitation conditions, but it does not prove exploitation is occurring. The CVE is not listed as KEV in the supplied bundle, and no cited evidence confirms active exploitation, a public proof of concept, or observed attacks.
Researcher notes
The supplied narrative says all versions through 1.4.2 are vulnerable, while the structured affected entry lists version "0" with default status "unaffected." This inconsistency lowers confidence in precise version modeling. The bundle also lacks root-cause details, affected code paths, exploitation telemetry, and a confirmed remediation version.
Mitigation direction
- Check MVPThemes, Wordfence, and Patchstack guidance for a confirmed fixed release or vendor mitigation.
- Deactivate Jawn on potentially affected sites where operationally feasible until confirmed remediation is available.
- Restrict administrative access and closely monitor account changes while remediation remains pending.
- If compromise is suspected, isolate the site and begin incident response before rotating credentials.
Validation and detection
- Inventory WordPress installations using Jawn and record each installed theme version.
- Treat versions through 1.4.2 as potentially affected pending vendor confirmation.
- Review administrator accounts for unexpected additions, privilege changes, or credential modifications.
- Examine relevant WordPress and hosting logs for unexplained administrative activity or site changes.
- Confirm remediation status against current MVPThemes, Wordfence, or Patchstack guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-266: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-78477 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineWordfence
Disclosed
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e0642c85-ee01-497c-8dc3-42e3ffc02995?source=cveCVE reference, Wordfence
- https://patchstack.com/database/wordpress/theme/jawn/vulnerability/wordpress-jawn-theme-1-4-2-privilege-escalation-vulnerabilityCVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.