dbcve.org
TestimonialsWordPress extension · Testimonials Project

CVE-2022-33191

MEDIUM · 5.4 CVSS v3.1 Published 2022-07-22
Fix available
A fix is available. Upgrade to after 3.0.1 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
Authenticated (contributor or higher user role) Stored Cross-Site Scripting (XSS) vulnerability in Chinmoy Paul's Testimonials plugin <= 3.0.1 at WordPress.

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

Authenticated (contributor or higher role) Stored Cross-Site Scripting (XSS) vulnerability in Chinmoy Paul's Testimonials WordPress plugin version 3.0.1 and below. The plugin fails to properly sanitize user input in the testimonials submission functionality, allowing authenticated attackers to inject malicious JavaScript that persists in the database and executes when other users view the testimonials.

MitigationUpdate the Testimonials plugin to the latest patched version. If no patch is available, remove the plugin. Additionally, review user permissions and ensure only trusted users have contributor or higher 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
TestimonialsWordPress extension
Affected:<= 3.0.1

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. Identify the installed Testimonials plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Testimonials. The version number is displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/testimonials-project-testimonials/ or via WP-CLI: wp plugin list --name='testimonials-project-testimonials'
    Affected if The installed version is 3.0.1 or lower
  2. Confirm the testimonials submission form is enabled
    Check if the plugin settings allow public or authenticated submissions. Look for options like 'Enable Submission', 'Allow Guest Submissions', or 'Submission Form' in the plugin settings page (Testimonials > Settings or similar). In the database, check the wp_options table for relevant option_name values related to submission settings.
    Affected if Submission functionality is enabled and accessible to authenticated users with contributor role or higher
  3. Verify user role permissions for testimonial submissions
    Go to WordPress admin > Users > Roles. Check if any untrusted user accounts have been assigned the Contributor, Author, Editor, or Administrator role. Review which users can access the testimonials submission form. Use WP-CLI: wp user list --role=contributor
    Affected if Untrusted or unknown user accounts exist with contributor or higher role who have access to the submission feature
  4. Inspect testimonial entries for suspicious stored content
    Access the WordPress admin testimonial list (Testimonials > All Testimonials or similar). Manually review entries for unusual script tags, javascript: URLs, event handlers (onload, onerror, onclick), or encoded content. For database inspection: SELECT * FROM wp_posts WHERE post_type='testimonial' AND (post_content LIKE '%<script%' OR post_content LIKE '%onload=%' OR post_content LIKE '%onerror=%')
    Affected if Any testimonial entries contain script tags, event handlers, or JavaScript code that was not intentionally added by administrators

You are affected if the Testimonials plugin version is 3.0.1 or lower AND the submission feature is enabled, allowing users with contributor or higher role to inject and store malicious JavaScript in testimonial entries.

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.

From vendor data
Upgrade available Upgrade to a release after 3.0.1
Interim mitigation

Update the Testimonials plugin to the latest patched version. If no patch is available, remove the plugin. Additionally, review user permissions and ensure only trusted users have contributor or higher access.

Fix this in Testimonials Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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