dbcve.org
Super TestimonialsWordPress extension · Codecabin

CVE-2024-9127

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-26
Fix available
A fix is available. Upgrade to after 3.0.0 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 Super Testimonials plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘alignment’ parameter in all versions up to, and including, 3.0.0 due to insufficient input sanitization and output escaping. 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.

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 Super Testimonials WordPress plugin (versions up to 3.0.0) contains a stored Cross-Site Scripting vulnerability in the 'alignment' parameter due to insufficient input sanitization and output escaping. Authenticated attackers with Contributor-level permissions or higher can inject malicious JavaScript that executes whenever users view pages containing the injected testimonial shortcode or widget.

MitigationUpdate the Super Testimonials plugin to version 3.0.1 or later. Until an update is available, restrict contributor-level user creation and review existing user accounts for malicious content in testimonial alignment settings.

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
Super TestimonialsWordPress extension
Affected:<= 3.0.0

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. Verify Super Testimonials plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Super Testimonials' by Codecabin. Note the installed version number shown.
    Affected if The plugin is installed and the version listed is 3.0.0 or lower.
  2. Check plugin version in file system
    Access the plugin directory via FTP or file manager: navigate to /wp-content/plugins/super-testimonials/ and open the main plugin file (usually super-testimonials.php or similar). Look for the 'Version:' header comment.
    Affected if The version declared in the plugin file header is 3.0.0 or lower.
  3. Inspect testimonial alignment settings in database
    Query the WordPress database posts table for testimonial custom post types (usually post_type 'testimonial' or similar) and examine any meta entries containing 'alignment'. Look for unusual characters, HTML tags, or script elements in alignment values.
    Affected if Any testimonial record contains HTML or JavaScript code (such as <script>, javascript:, onerror=, etc.) in alignment metadata.
  4. Review pages with testimonial shortcodes for XSS payload execution
    Search post content for [super_testimonial] shortcode or testimonial widget usage. View these pages in a browser and check browser console for JavaScript errors or inspect page source for injected scripts in alignment attributes.
    Affected if Viewing a page with a testimonial displays unexpected alerts, console errors, or contains unsanitized script tags in the rendered alignment HTML.
  5. Audit user accounts with Contributor-level access
    In WordPress admin, go to Users and review all accounts with role 'Contributor' or higher. Check if any unknown or suspicious accounts exist that could have added malicious alignment values.
    Affected if Unrecognized user accounts with Contributor or higher permissions exist, or known users have added testimonials with suspicious alignment content.

A user is affected if the Super Testimonials plugin is installed at version 3.0.0 or below AND any testimonial contains unsanitized script or HTML code in alignment settings that executes when pages are viewed.

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

Update the Super Testimonials plugin to version 3.0.1 or later. Until an update is available, restrict contributor-level user creation and review existing user accounts for malicious content in testimonial alignment settings.

Recommended fix Moderate confidence

Super Testimonials version 3.0.1 or latest available

  1. Backup your WordPress site before making any changes
  2. Update the Super Testimonials plugin to version 3.0.1 or the latest available version from the WordPress plugin repository
  3. Verify the plugin update was successfully applied
  4. Confirm the 'alignment' parameter now properly sanitizes and escapes user input

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

Fix this in Super Testimonials Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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