dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-7048

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Photo Gallery by 10Web – Mobile-Friendly Image Gallery plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'order_by' parameter in all versions up to, and including, 1.8.40 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is exploitable by embedding a malicious shortcode in a post or draft, allowing the injected SQL to execute when the shortcode is rendered.

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 Photo Gallery by 10Web plugin fails to properly escape and sanitize the 'order_by' parameter, allowing authenticated users with contributor-level access to inject time-based blind SQL queries via shortcode embedding. The vulnerability exists because the parameter is not passed through appropriate escaping functions and the existing SQL query lacks prepared statement parameterization.

MitigationUpdate the plugin to version 1.8.41 or later. Until patched, restrict contributor-level user permissions and review shortcode usage in published content.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Verify Photo Gallery by 10Web plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Photo Gallery by 10Web' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active
  2. Check installed plugin version
    In the plugins list, click on the plugin name or view the plugin details to see the installed version number. Compare this against version 1.8.41.
    Affected if Installed version is lower than 1.8.41 (versions prior to the patch are vulnerable)
  3. Identify contributor-level user accounts
    In WordPress admin, go to Users > All Users and look for any accounts with the 'Contributor' role.
    Affected if At least one contributor-level user account exists in the WordPress installation
  4. Search for gallery shortcode usage in published content
    In WordPress admin, go to Posts or Pages. Search for content containing the shortcode [gallery] or [wd_gallery] - or use a database query to search the wp_posts table for these shortcode strings in the post_content field.
    Affected if Any posts or pages contain gallery shortcodes and are accessible to contributors

A user is affected if the plugin is installed with a version below 1.8.41, contributor-level accounts exist, and gallery shortcodes are present in accessible content.

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 plugin to version 1.8.41 or later. Until patched, restrict contributor-level user permissions and review shortcode usage in published content.

Recommended fix Moderate confidence

Version after 1.8.40 (check WordPress plugin repository for latest fixed release)

  1. 1. Log in to WordPress admin dashboard with contributor-level or higher access
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Photo Gallery by 10Web' plugin
  4. 4. Check if an update is available. If updates are available, update to the latest version that addresses the SQL injection vulnerability in the 'order_by' parameter
  5. 5. After updating, verify the fix by testing shortcode functionality with various order_by parameters to confirm SQL injection is no longer possible
  6. 6. Review any security settings or additional hardening recommendations from the plugin developer
Caveat Minor - standard plugin update, review any changed settings after upgrade

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-2026-7048 — 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-2026-7048 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