Skip to content
FortressDiscuss your projectMenu

CVE-2026-9677

Shariff for WordPress: Admin+ Stored Cross Site Scripting

Product
Shariff for WordPress (WordPress plugin)
Versions
Up to and including 1.0.11 · no known fix
Severity
LowCVSS score 3.5 · WPScan
CVE
CVE-2026-9677, assigned by WPScan
Found by
Mustafa Ahmed, Fortress MSSP
Published
November 11, 2026CVE published by WPScan on June 27, 2026

Description

The Shariff for WordPress Shariff for WordPress plugin through 1.0.11 does not sanitize or escape the shariff_infourl setting before outputting it in the frontend HTML via the generateshariff() function, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

From the CVE record · CWE-79 Cross-Site Scripting (XSS)

Technical analysis

generateshariff() builds the Shariff container markup by string concatenation and inserts the stored shariff_infourl option straight into the data-info-url attribute via get_option(), with no esc_attr()/esc_url() or other filtering. Neighbouring values such as shariff_twittervia, shariff_temp and shariff_ttl are at least passed through filter_var(..., FILTER_SANITIZE_STRING), but the Info URL is not, so a stored value containing a double quote can close the attribute and add arbitrary markup to the frontend HTML.

Vulnerable: shariff-wp.php, version 1.0.11
function generateshariff($serv,$services,$image) {
	if (get_option('shariff_twittervia',"") != "") {
		$twittervia = ' data-twitter-via="'.filter_var(get_option('shariff_twittervia',""),FILTER_SANITIZE_STRING).'"';
	}
	return '<div class="shariff"'.$twittervia.' data-title="'.get_the_title().'" data-info-url="'.get_option('shariff_infourl',"http://ct.de/-2467514").'" data-backend-url="'.plugins_url( 'backend/index.php', __FILE__ ).'" data-temp="'.filter_var(get_option('shariff_temp',"/tmp"),FILTER_SANITIZE_STRING).'" data-ttl="'.filter_var(get_option('shariff_ttl',"60"),FILTER_SANITIZE_STRING).'" data-service="'.$serv.'" data-services=\''.$services.'\' data-image="'.$image.'" data-url="'.get_permalink().'" data-lang="'.__('en', 'shariff').'" data-theme="'.get_option('shariff_color',"colored").'" data-orientation="'.get_option('shariff_orientation',"horizontal").'"></div>';
}

Fortress’s reading of the public source code at the versions shown.

Proof of concept

No fixed version exists. WPScan published this proof of concept on June 5, 2026.

1. Log in as an Administrator
2. Go to Settings > Shariff (wp-admin/options-general.php?page=shariff)
3. Intercept the settings save request and inject the following payload into the shariff_infourl parameter:

"><img src=x onerror=alert(document.domain)>

4. Visit any published post page (even as an unauthenticated user)
5. The XSS payload executes because the Info URL value is output unescaped in the data-info-url HTML attribute

Severity

WPScan rates it 3.5 (low). CISA’s ADP scores it 4.8 (medium) in the CVE record.

  • CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:NCISA ADP

Remediation

WPScan's advisory lists no known fix. The CVE record lists Shariff for WordPress versions up to and including 1.0.11 as affected.

Disclosure timeline

  1. CVE ID reserved by WPScan.
  2. WPScan advisory published.
  3. CVE published by WPScan.
  4. Published on this site.

Credit

Found and reported by Mustafa Ahmed of Fortress MSSP. The CVE record credits Mustafa Ahmed as finder and WPScan as coordinator.

WPScan's advisory lists Mustafa Ahmed as original researcher and submitter, with fortressmssp.com as the submitter's website.

References