dbcve.org
GreenshiftWordPress extension · Wpsoul

CVE-2023-22707

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-27
Fix available
A fix is available. Upgrade to after 4.9.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
Auth. (author+) Cross-Site Scripting (XSS) vulnerability in Wpsoul Greenshift – animation and page builder blocks plugin <= 4.9.9 versions.

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 · moderate confidence

This is an authenticated Cross-Site Scripting (XSS) vulnerability in the Greenshift WordPress plugin affecting versions 4.9.9 and below. Attackers with author-level permissions or higher can inject malicious JavaScript into plugin functionality, which executes when other users view affected pages in the admin dashboard or frontend.

MitigationUpdate the Greenshift plugin to a version newer than 4.9.9 once the vendor releases a patch. Until then, restrict user permissions to only trusted roles and consider additional input sanitization measures.

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
GreenshiftWordPress extension
Affected:<= 4.9.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 if Greenshift plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Greenshift' or 'Wpsoul Greenshift' in the installed plugins list, or inspect the /wp-content/plugins/ directory for a folder containing 'greenshift' in the name
    Affected if The Greenshift plugin appears in the installed plugins list
  2. Verify the installed version number
    In WordPress admin > Plugins > Installed Plugins, locate Greenshift and note the version number displayed below the plugin name. Alternatively, open the plugin's main PHP file and check the Version header comment or version constant
    Affected if The installed version is 4.9.9 or lower (any version up to and including 4.9.9)
  3. Confirm plugin status is active
    In WordPress admin > Plugins, verify that Greenshift shows an 'Active' status under the plugin name, not 'Inactive' or 'Network Deactivated'
    Affected if The plugin status is Active and running on the site
  4. Identify users with author-level or higher access
    In WordPress admin > Users, examine the Role column for each user account. Users assigned Author, Editor, Administrator, or any custom role with equivalent or higher permissions can trigger this vulnerability
    Affected if One or more user accounts have Author, Editor, Administrator, or higher-level roles

The environment is affected if the Greenshift plugin version is 4.9.9 or lower AND the plugin is active on the site, since an authenticated user with author-level permissions could inject malicious scripts.

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 4.9.9
Interim mitigation

Update the Greenshift plugin to a version newer than 4.9.9 once the vendor releases a patch. Until then, restrict user permissions to only trusted roles and consider additional input sanitization measures.

Recommended fix Moderate confidence

Upgrade to Greenshift version 5.0 or later (latest version recommended)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Greenshift plugin (Greenshift – animation and page builder blocks)
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. After updating, verify the plugin is running version 5.0 or higher
Caveat Review plugin settings after upgrade as minor layout/option changes may occur between major versions

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

Fix this in Greenshift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22707 — 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-2023-22707 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