CVE-2023-48275
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Trustindex.Io Widgets for Google Reviews.This issue affects Widgets for Google Reviews: 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 confidenceThe Trustindex.Io Widgets for Google Reviews plugin for WordPress contains an unrestricted file upload vulnerability (CWE-434) in versions up to 11.0.2, allowing attackers to upload files with dangerous types (e.g., PHP scripts) due to insufficient validation of file extensions or content during the upload process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
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.
-
Verify the Trustindex plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Trustindex.Io Widgets for Google Reviews' or check the plugin directory /wp-content/plugins/ for a folder containing 'trustindex' in the nameAffected if The plugin is present on the WordPress site
-
Check the installed plugin versionIn WordPress admin, click on the plugin to view its details and note the version number, or read the main plugin PHP file header for the 'Version' fieldAffected if The version is 11.0.2 or lower (any version up to and including 11.0.2)
-
Confirm the upload functionality is accessibleCheck if the plugin settings or any public-facing page includes a review upload or file submission form. Inspect the HTML source or check network requests for upload endpoints (typically containing 'upload', 'file', or 'attachment' in the URL)Affected if The file upload feature is enabled or exposed on the site
-
Verify upload directory PHP execution statusCheck the web server configuration and .htaccess file in the wp-content/uploads directory for restrictions on PHP file execution. Look for directives like 'php_flag engine off' or similar PHP execution blocksAffected if PHP execution is allowed in upload directories (no restrictions found)
The site is affected if the Trustindex.Io Widgets for Google Reviews plugin is installed with version 11.0.2 or lower and the file upload feature is accessible, especially if upload directories allow PHP execution.
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.
From vendor dataRestrict file uploads by implementing strict allowlist-based file type validation, verifying actual file content (magic bytes), storing uploaded files outside the web root or in non-executable locations, and disabling PHP execution in upload directories.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48275 — 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-2023-48275 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