The AI Agent by SiteGround plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.2.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to upload images to the WordPress media library, bypassing the upload_files capability restriction that Contributors are normally subject to, as authenticated attackers with Contributor-level access or above can satisfy the endpoint's nonce and permission checks. The sg_ai_studio_gutenberg_nonce required by the endpoint is emitted to any user with block editor access — including Contributors — making the absent upload_files check the sole barrier to exploitation.
CVE-2026-17153
Score 5.3 from GitHub Security Advisory published 2026-08-20. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 20, 2026
Last Modified
August 20, 2026
References (7)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/sg-ai-studio/tags/1.2.6/core/Helper/Helper.php#L1077
- security@wordfencehttps://plugins.trac.wordpress.org/browser/sg-ai-studio/tags/1.2.6/core/Helper/Helper.php#L604
- security@wordfencehttps://plugins.trac.wordpress.org/browser/sg-ai-studio/tags/1.2.6/core/Rest/Gutenberg.php#L118
- security@wordfencehttps://plugins.trac.wordpress.org/browser/sg-ai-studio/tags/1.2.6/core/Rest/Rest.php#L325
- security@wordfencehttps://plugins.trac.wordpress.org/browser/sg-ai-studio/tags/1.2.6/core/Rest/Rest.php#L474
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3654622%40sg-ai-studio&new=3654622%40sg-ai-studio
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/6280f40e-2998-43d4-a78f-b393e4f36df5?source=cve
Vendor Advisories for CVE-2026-17153(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 16:34 UTCEG score recompute
- 2026-08-20 16:34 UTCGHSA enrichment
- 2026-08-20 15:44 UTCEG score recompute
- 2026-08-20 15:44 UTCGHSA enrichment
- 2026-08-20 12:50 UTCEG score recompute
- 2026-08-20 12:50 UTCGHSA enrichment
- 2026-08-20 06:20 UTCEG score recompute
- 2026-08-20 05:37 UTCEG score recompute
- 2026-08-20 05:37 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-17153?
When was CVE-2026-17153 disclosed?
Is CVE-2026-17153 actively exploited?
What is the CVSS score of CVE-2026-17153?
How do I remediate CVE-2026-17153?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-17153
Is Your Infrastructure Affected by CVE-2026-17153?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.