CVE-2025-14726
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 · uneditedThe Widgets for Social Photo Feed plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on the '/trustindex_feed_hook_instagram/troubleshooting' and '/trustindex_feed_hook_instagram/submit-data' REST API endpoints in all versions up to, and including, 1.8. This makes it possible for unauthenticated attackers to access and update plugin settings.
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 confidenceThe Widgets for Social Photo Feed WordPress plugin lacks capability checks on two REST API endpoints (/trustindex_feed_hook_instagram/troubleshooting and /trustindex_feed_hook_instagram/submit-data), allowing unauthenticated attackers to access and modify plugin settings. This is a classic Insecure Direct Object Reference (IDOR) combined with missing authorization on REST routes.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Confirm plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Widgets for Social Photo Feed' or check the plugin directory /wp-content/plugins/ for a folder starting with 'widgets-for-social-photo-feed' or 'trustindex'Affected if Plugin is installed and active
-
Identify installed versionIn WordPress admin Plugins list, click on the plugin to view details, or inspect the main plugin file (e.g., widgets-for-social-photo-feed.php) and look for the 'Version:' header commentAffected if Version is lower than 1.9 or version cannot be determined (indicating older unpatched release)
-
Test REST endpoint accessibilitySend a GET request to /wp-json/trustindex_feed_hook_instagram/troubleshooting and /wp-json/trustindex_feed_hook_instagram/submit-data using curl or a browser (no authentication required)Affected if Endpoints return HTTP 200 OK with any response body (even if seemingly empty), indicating the routes are exposed without authorization checks
-
Verify endpoint behaviorInspect the response from the troubleshooting endpoint - if it returns plugin settings, configuration data, or any JSON structure, the vulnerability is presentAffected if Endpoint returns any plugin data or accepts submissions without requiring WordPress user authentication
A user is affected if the Widgets for Social Photo Feed plugin is installed with a version lower than 1.9 and the /trustindex_feed_hook_instagram REST endpoints are accessible without authentication.
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 dataAdd WordPress capability checks (e.g., current_user_can('manage_options')) to both REST API endpoints before processing any data, and update to version 1.9 or later when available.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14726 — 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-14726 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