dbcve.org
Advanced IframeWordPress extension · Tinywebgallery

CVE-2023-51690

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to after 2023.8 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Advanced iFrame allows Stored XSS.This issue affects Advanced iFrame: from n/a through 2023.8.

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

Stored Cross-site Scripting (XSS) vulnerability in the Advanced iFrame WordPress plugin allows attackers to inject malicious JavaScript through unsanitized input fields, which is then executed when administrators or users view the affected content.

MitigationImplement proper input validation and output encoding for all user-supplied data before rendering in HTML context. Use WordPress built-in sanitization functions and Content Security Policy headers.

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
Advanced IframeWordPress extension
Affected:<= 2023.8

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. Confirm Advanced iFrame plugin installation
    In WordPress admin, navigate to Plugins > Instored Plugins and locate 'Advanced iFrame' or check the plugin files for version information in the main plugin file header comment
    Affected if Plugin is installed and active
  2. Identify installed plugin version
    View the plugin version number in the plugin list or in the plugin's main PHP file (typically advanced-iframe.php) in the plugin directory
    Affected if Version number is 2023.8 or lower
  3. Check plugin input fields for unsanitized data
    Navigate to the Advanced iFrame settings page in WordPress admin and inspect input fields such as iframe shortcode parameters, custom CSS, or URL fields for any existing malicious script tags
    Affected if Input fields contain unsanitized HTML or JavaScript content that could execute in admin or user contexts

If the Advanced iFrame plugin version is 2023.8 or lower and unsanitized user-supplied data exists in plugin input fields, the environment is affected by this stored XSS 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.

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

Implement proper input validation and output encoding for all user-supplied data before rendering in HTML context. Use WordPress built-in sanitization functions and Content Security Policy headers.

Fix this in Advanced Iframe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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