dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10637

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Social Feed Gallery plugin for WordPress is vulnerable to Information Exposure in versions less than, or equal to, 4.9.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to exfiltrate Instagram profile and media data from any account the site owner connected to their site.

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 confidence

The Social Feed Gallery WordPress plugin <=4.9.2 contains a broken access control vulnerability allowing unauthenticated attackers to retrieve Instagram profile and media data from any account connected to the affected site. The plugin fails to verify user authorization before returning sensitive social media data through its feed functionality.

MitigationUpdate the Social Feed Gallery plugin to the latest version (above 4.9.2) which includes proper authorization checks. Until updated, consider restricting access to the affected endpoints via web server configuration or monitoring for unauthorized Instagram data access attempts.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 if Social Feed Gallery plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'social-feed-gallery' or 'social-feed-gallery-wp' or similar. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to look for 'Social Feed Gallery' in the list.
    Affected if The plugin folder exists in the WordPress installation's plugins directory.
  2. Determine the installed version of the plugin
    If the plugin is installed, open the main plugin file (usually social-feed-gallery.php or similar in the plugin folder) and look for the 'Version' header in the plugin comments at the top of the file. Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' entry.
    Affected if The version listed is 4.9.2 or any version lower than 4.9.2.
  3. Verify if Instagram feeds are configured on the site
    Check the WordPress admin panel for the Social Feed Gallery plugin settings, or examine the site frontend to see if any Instagram feeds are being displayed. Inspect page source for elements like 'sfg-feed', 'instagram-feed', or API endpoint calls related to Instagram.
    Affected if Instagram feeds are active or configured on the site, meaning the vulnerable functionality is in use.
  4. Test unauthenticated access to Instagram data endpoints
    Use a web browser or tool like curl to access common plugin API endpoints without providing any authentication. Typical endpoints may include paths like /wp-json/sfg/v1/feed/instagram or similar /?action=instagram_feed requests. Check the HTTP response for Instagram profile or media data.
    Affected if The endpoint returns Instagram profile information, media URLs, or other sensitive social media data without requiring login or authentication.

If the Social Feed Gallery plugin version is 4.9.2 or lower AND Instagram feeds are configured on the site, the environment is likely affected by this unauthenticated data exposure vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Social Feed Gallery plugin to the latest version (above 4.9.2) which includes proper authorization checks. Until updated, consider restricting access to the affected endpoints via web server configuration or monitoring for unauthorized Instagram data access attempts.

Recommended fix Moderate confidence

Version 4.9.3 or later (latest available version from wordpress.org)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Social Feed Gallery plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, manually download the latest version from wordpress.org/plugins/social-feed-gallery and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly and connected Instagram accounts are working as expected

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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