dbcve.org
SeopressWordPress extension

CVE-2024-1168

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to after 7.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The SEOPress – On-site SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's social image URL in all versions up to, and including, 7.9 due to insufficient input sanitization and output escaping on user supplied image URLs. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SEOPress WordPress plugin (versions up to 7.9) contains a stored XSS vulnerability in its social image URL field. Authenticated attackers with contributor-level or higher permissions can inject arbitrary JavaScript through unsanitized image URLs, which executes when other users access affected pages.

MitigationUpdate SEOPress to version 7.10 or later which patches the vulnerability. Additionally, audit user accounts with contributor-level and above permissions to ensure no malicious actors have elevated access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SeopressWordPress extension
Affected:<= 7.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check SEOPress plugin version
    In WordPress admin, go to Plugins > Installed Plugins > SEOPress and look at the Version number. Alternatively, check the main plugin file header or the seopress.php file for the 'Version' constant.
    Affected if The installed version is 7.9 or lower (any version up to and including 7.9)
  2. Verify social image URL field exists
    Navigate to SEOPress settings: SEO > Social > Social Networks. Locate the 'Image URL' or 'Default OG Image' field in the Facebook/Open Graph section.
    Affected if The social image URL field is present and configurable in the plugin settings
  3. Check user roles with contributor-level or higher access
    In WordPress admin, go to Users > All Users and review the role column. Identify any accounts with Contributor, Author, Editor, or Administrator roles.
    Affected if There are user accounts with contributor-level (or higher) permissions in the system
  4. Inspect page source for social meta tags
    View the source code (HTML) of a published page on the site. Look for meta tags containing 'og:image' or 'twitter:image' that reference the SEOPress social image URL.
    Affected if Social meta tags generated by SEOPress are present in page output, indicating the vulnerable feature is active

The environment is affected if SEOPress version is 7.9 or lower AND the social image URL feature is enabled and outputting meta tags on pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.9
Interim mitigation

Update SEOPress to version 7.10 or later which patches the vulnerability. Additionally, audit user accounts with contributor-level and above permissions to ensure no malicious actors have elevated access.

Recommended fix High confidence

SEOPress version 7.9.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the SEOPress plugin
  4. Check if an update is available and install the latest version (version 7.9.1 or higher)
  5. Alternatively, download the latest version from wordpress.org/plugins/seopress/ and upload via Plugins > Add New > Upload Plugin
  6. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seopress Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1168 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data