{"api_version":"1","generated_at":"2026-04-28T12:14:17+00:00","cve":"CVE-2026-6809","urls":{"html":"https://cve.report/CVE-2026-6809","api":"https://cve.report/api/cve/CVE-2026-6809.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-6809","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-6809"},"summary":{"title":"Social Post Embed <= 2.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Threads Embed","description":"The Social Post Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Threads embed handler in all versions up to, and including, 2.0.1. This is due to insufficient input sanitization and output escaping on the user-supplied URL. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.","state":"PUBLISHED","assigner":"Wordfence","published_at":"2026-04-28 06:16:04","updated_at":"2026-04-28 06:16:04"},"problem_types":["CWE-79","CWE-79 CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')"],"metrics":[{"version":"3.1","source":"security@wordfence.com","type":"Primary","score":"6.4","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","baseScore":6.4,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"6.4","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","data":{"baseScore":6.4,"baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"}}],"references":[{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L50","name":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L50","refsource":"security@wordfence.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/4c16841d-8878-4328-a5dc-113d213cca33?source=cve","name":"https://www.wordfence.com/threat-intel/vulnerabilities/id/4c16841d-8878-4328-a5dc-113d213cca33?source=cve","refsource":"security@wordfence.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.1/inc/threads.php#L64","name":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.1/inc/threads.php#L64","refsource":"security@wordfence.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L61","name":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L61","refsource":"security@wordfence.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/trunk/inc/threads.php#L64","name":"https://plugins.trac.wordpress.org/browser/social-post-embed/trunk/inc/threads.php#L64","refsource":"security@wordfence.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L49","name":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L49","refsource":"security@wordfence.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-6809","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6809","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"dartiss","product":"Social Post Embed","version":"affected 2.0.1 semver","platforms":[]}],"timeline":[{"source":"CNA","time":"2026-04-21T17:36:12.000Z","lang":"en","value":"Vendor Notified"},{"source":"CNA","time":"2026-04-27T15:57:20.000Z","lang":"en","value":"Disclosed"}],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"Anas Mokhtari","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Social Post Embed","vendor":"dartiss","versions":[{"lessThanOrEqual":"2.0.1","status":"affected","version":"0","versionType":"semver"}]}],"credits":[{"lang":"en","type":"finder","value":"Anas Mokhtari"}],"descriptions":[{"lang":"en","value":"The Social Post Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Threads embed handler in all versions up to, and including, 2.0.1. This is due to insufficient input sanitization and output escaping on the user-supplied URL. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page."}],"metrics":[{"cvssV3_1":{"baseScore":6.4,"baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-79","description":"CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-04-28T04:28:21.151Z","orgId":"b15e7b5b-3da4-40ae-a43c-f7aa60e62599","shortName":"Wordfence"},"references":[{"url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/4c16841d-8878-4328-a5dc-113d213cca33?source=cve"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/trunk/inc/threads.php#L64"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.1/inc/threads.php#L64"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L49"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L50"},{"url":"https://plugins.trac.wordpress.org/browser/social-post-embed/tags/2.0.2/inc/threads.php#L61"}],"timeline":[{"lang":"en","time":"2026-04-21T17:36:12.000Z","value":"Vendor Notified"},{"lang":"en","time":"2026-04-27T15:57:20.000Z","value":"Disclosed"}],"title":"Social Post Embed <= 2.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Threads Embed"}},"cveMetadata":{"assignerOrgId":"b15e7b5b-3da4-40ae-a43c-f7aa60e62599","assignerShortName":"Wordfence","cveId":"CVE-2026-6809","datePublished":"2026-04-28T04:28:21.151Z","dateReserved":"2026-04-21T17:19:28.939Z","dateUpdated":"2026-04-28T04:28:21.151Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-04-28 06:16:04","lastModifiedDate":"2026-04-28 06:16:04","problem_types":["CWE-79","CWE-79 CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')"],"metrics":{"cvssMetricV31":[{"source":"security@wordfence.com","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","baseScore":6.4,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"NONE"},"exploitabilityScore":3.1,"impactScore":2.7}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"6809","Ordinal":"1","Title":"Social Post Embed <= 2.0.1 - Authenticated (Contributor+) Stored","CVE":"CVE-2026-6809","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"6809","Ordinal":"1","NoteData":"The Social Post Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Threads embed handler in all versions up to, and including, 2.0.1. This is due to insufficient input sanitization and output escaping on the user-supplied URL. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.","Type":"Description","Title":"Social Post Embed <= 2.0.1 - Authenticated (Contributor+) Stored"}]}}}