Security readout for executives and security teams
Plain-English summary
CVE-2023-6708 lets a logged-in WordPress author abuse SVG uploads in the SVG Support plugin to store scripts that run when someone views affected content. Business risk depends on whether authors are allowed to upload SVG files. The impact is moderate: account/session exposure or page tampering is plausible, but attacker access is required.
Executive priority
Treat this as a moderate-priority web content integrity issue. Prioritize sites with many authors, external contributors, or customer-facing WordPress content. Remediation should be straightforward: update the plugin where possible and restrict who can upload SVG files.
Technical view
SVG Support for WordPress through 2.5.7 has stored XSS in SVG upload handling from insufficient sanitization and output escaping. The advisory says this can occur even with upload sanitization enabled, and notes a content-type bypass as of 2.5.6. Exploitation requires authenticated author-level access or higher and administrator-enabled SVG uploads for authors.
Likely exposure
Exposure is likely on WordPress sites running SVG Support up to 2.5.7 where authors or higher roles can upload SVG files. Sites with only trusted administrators uploading SVGs are less exposed. Plugin metadata in the bundle is incomplete, so confirm against installed plugin versions and configuration.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The weakness is still practical in contributor-heavy sites because it only requires low-privileged authenticated access plus a permissive SVG upload configuration. User interaction is required when someone views affected content.
Researcher notes
The main constraints are authenticated author-level access, enabled SVG uploads for authors, and user viewing of injected content. The advisory explicitly warns sanitization can be bypassed, so validation should include configuration review and uploaded media review, not only checking whether sanitization is enabled.
Mitigation direction
- Update SVG Support beyond 2.5.7 if vendor guidance provides a fixed release.
- Restrict SVG upload permission to trusted administrators only.
- Disable SVG uploads if they are not operationally required.
- Review vendor and WordPress plugin guidance for current remediation details.
- Remove or quarantine SVGs uploaded by untrusted author-level accounts.
Validation and detection
- Inventory WordPress sites using the SVG Support plugin.
- Confirm installed SVG Support versions and flag 2.5.7 or earlier.
- Check whether author-level users can upload SVG files.
- Review media uploads for SVGs submitted by non-administrator accounts.
- Review audit logs for recent SVG uploads and related page updates.
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-2023-6708 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
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/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.
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:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/72bcfd2a-6803-4073-8fa9-62bcf0a10571?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/svg-support/trunk/svg-support.php#L110CVE reference
- https://plugins.trac.wordpress.org/browser/svg-support/trunk/functions/attachment.php#L235CVE reference
- https://wordpress.org/plugins/svg-support/CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3133760%40svg-support&new=3133760%40svg-support&sfp_email=&sfph_mail=CVE reference
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.