GreenshiftWordPress extension · Wpsoul
CVE-2025-30873
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpsoul Greenshift greenshift-animation-and-page-builder-blocks allows Stored XSS.This issue affects Greenshift: from n/a through <= 11.0.2.
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 confidenceStored XSS vulnerability in Greenshift WordPress plugin allows attackers to inject malicious JavaScript through plugin blocks. The unsanitized input is stored in the database and executes when other users view affected pages, potentially leading to session hijacking or privilege escalation.
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
< 11.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Greenshift plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Greenshift and read the Version number. Alternatively, check the main plugin file (greenshift-animation-and-design/lib/core.php or similar) for the 'Version' header.Affected if Version is lower than 11.1 (e.g., 11.0, 10.9, etc.)
-
Identify pages using Greenshift blocksQuery the WordPress posts table: SELECT ID, post_title, post_type FROM wp_posts WHERE post_content LIKE '%wp:greenshift%' OR post_content LIKE '%<!-- wp:greenshift%' LIMIT 50;Affected if Any pages, posts, or custom post types contain Greenshift block markup in post_content
-
Inspect stored content for script injectionSearch post_content for script tags or event handlers: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onload=%' OR post_content LIKE '%onerror=%'; Manually review the content of identified posts for suspicious JavaScript.Affected if Any stored content contains unsanitized script tags, inline event handlers (onload, onerror, onclick), or foreign JavaScript URLs
-
Check for malicious scripts in custom codeIf custom blocks or code using Greenshift API exist, review those PHP/JS files for user input being output without sanitization (e.g., missing esc_html, esc_attr, or wp_kses_post).Affected if Custom code outputs user-submitted data without proper sanitization functions
-
Review recent admin or editor sessionsCheck WordPress user sessions and audit logs for unexpected privilege escalation, new admin accounts, or suspicious user creation occurring after the plugin was in use.Affected if Unknown admin accounts exist or suspicious activity occurred in logs
You are affected if Greenshift plugin version is below 11.1 AND any pages use Greenshift blocks AND malicious scripts are found stored in post content or custom code.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.1
Update Greenshift plugin to latest version immediately. Audit existing pages using the plugin for any injected malicious scripts and remove them. Implement output encoding on any custom code using the plugin.
11.1
- Backup your WordPress site and database before updating
- Navigate to Dashboard > Plugins in your WordPress admin
- Locate the Greenshift (greenshift-animation-and-page-builder-blocks) plugin
- Click 'Update now' if an update to version 11.1 is available, or manually download version 11.1 from the WordPress plugin repository and upload it
- After updating, verify the plugin shows version 11.1 in the plugins list
- Clear any caching plugins and server-side caches to ensure the fix is fully applied
- Test critical frontend functionality to confirm the plugin continues to work as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Greenshift
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30873 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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