Security readout for executives and security teams
Plain-English summary
Textpattern CMS 4.9.0 can place insufficiently escaped user input into Atom feed XML. A malicious value may later run script in a feed reader or CMS aggregator that renders the feed unsafely. Business impact is mainly session or content-context abuse for readers of affected feeds, not server takeover based on the supplied sources.
Executive priority
Treat as a moderate web-content integrity issue. Prioritize internet-facing Textpattern 4.9.0 sites and environments where feeds are consumed by staff tools, partner portals, or authenticated CMS aggregators.
Technical view
The issue is a second-order XSS in Atom feed generation: user-supplied parameters such as category may be reflected into Atom elements without proper escaping. Exploitation requires a victim or downstream aggregator to consume and render the feed in a DOM-unsafe way. CVSS 3.1 is 6.1, with network access, low complexity, no privileges, and required user interaction.
Likely exposure
Organizations running Textpattern CMS 4.9.0 with public Atom feeds are the main exposure. Risk increases where anonymous or low-trust users can influence categories or feed metadata, and where downstream readers ingest the feed into privileged CMS or intranet contexts.
Exploitation context
The bundle includes an exploit-tagged Packet Storm reference, but KEV is false and no source states active exploitation. The attack depends on stored or reflected feed content later being consumed by software that inserts feed data into the DOM unsafely.
Researcher notes
Evidence names only Textpattern CMS 4.9.0. The source bundle does not provide a vendor advisory, patch version, or confirmed exploit-in-the-wild status. Analysis should avoid broad version assumptions until vendor guidance or additional CVE data confirms them.
Mitigation direction
- Identify and prioritize any Textpattern CMS 4.9.0 deployments.
- Check Textpattern vendor guidance for fixed releases or official mitigations.
- Restrict who can create or modify feed-influencing metadata.
- Sanitize existing categories and feed metadata for suspicious script-like content.
- Avoid rendering untrusted feed fields with unsafe DOM insertion methods.
Validation and detection
- Inventory Textpattern instances and confirm exact installed versions.
- Review public Atom feeds for unexpected user-controlled metadata.
- Inspect recent category and content changes without executing embedded content.
- Test feed rendering with harmless marker strings in a controlled environment.
- Confirm downstream feed readers encode feed fields before DOM insertion.
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-116: 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 lookupCWE-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-2026-32986 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
- Medium
- CVSS
- 6.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:N
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
2 official scoresWe 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:N2.82.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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
- Packet Storm listing (Textpattern 4.9.0 Second-Order XSS via Atom Feed Injection)CVE reference, VulnCheck · exploit
- Vendor siteCVE reference, VulnCheck · product
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.