Security readout for executives and security teams
Plain-English summary
CVE-2025-32582 is a stored cross-site scripting issue in the WordPress WP AutoKeyword plugin through version 1.0. If exploited, malicious script could be saved in site content and run when a user views the affected page, creating risk to sessions, content integrity, and visitor trust.
Executive priority
Treat this as a high-priority WordPress plugin exposure where the main business risk is malicious script persisting on a public site. Prioritize internet-facing sites and sites handling authenticated users or customer traffic.
Technical view
The issue is CWE-79 improper input neutralization during web page generation in EXEIdeas International WP AutoKeyword. The CVSS 3.1 score is 7.1: network reachable, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to WordPress sites running the WP AutoKeyword plugin at version 1.0 or earlier. The source bundle does not provide CPEs or deployment prevalence, so asset inventory is needed to confirm exposure.
Exploitation context
The source bundle does not claim active exploitation, and KEV status is false. Exploitation would require a user interaction path where stored malicious content is later rendered in a browser. No exploit steps are provided in the cited sources.
Researcher notes
Patch and exploit details are incomplete in the provided bundle. The affected metadata lists limited version information, while the description and Patchstack title identify WP AutoKeyword through 1.0. Validate against the CVE record and Patchstack before final remediation decisions.
Mitigation direction
- Inventory WordPress sites for the wp-autokeyword plugin and installed version.
- Check Patchstack and vendor guidance for an official fixed version or mitigation.
- Upgrade only to a vendor-confirmed fixed release, if available.
- Disable or replace the plugin if no maintained fix is available.
- Review administrator sessions and content changes on exposed sites.
Validation and detection
- Confirm whether WP AutoKeyword is installed on each WordPress instance.
- Record the plugin version and flag versions 1.0 or earlier.
- Review public pages and plugin-generated content for unexpected script-like markup.
- Check security monitoring for suspicious WordPress content modifications.
- Verify remediation by confirming the vulnerable plugin is updated, removed, or disabled.
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-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2025-32582 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
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- 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://patchstack.com/database/Wordpress/Plugin/wp-autokeyword/vulnerability/wordpress-wp-autokeyword-plugin-1-0-cross-site-scripting-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.