dbcve.org
Full FrameWordPress extension · Catchthemes

CVE-2024-44010

MEDIUM · 5.1 CVSS v3.1 Published 2024-10-06
Fix available
A fix is available. Upgrade to 2.7.3 / 4.3.1 or later.
See remediation →
55/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 catchthemes Full frame full-frame allows Stored XSS.This issue affects Full frame: from n/a through <= 2.7.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 confidence

A Stored Cross-Site Scripting (XSS) vulnerability exists in the catchthemes Full frame WordPress theme (versions <= 2.7.2). The vulnerability stems from improper input neutralization during web page generation, allowing an attacker to inject malicious scripts that persist in the database and execute when other users view the affected pages.

MitigationUpdate to the latest version of the Full frame theme once a patch is released, or implement proper input sanitization and output encoding on all user-supplied data before rendering in HTML contexts.

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
Full FrameWordPress extension
Affected:< 2.7.3< 4.3.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Full Frame theme is installed
    Access WordPress admin dashboard, go to Appearance > Themes, and verify if the Full Frame theme is present and activated
    Affected if Full Frame theme is installed and active on the WordPress site
  2. Check installed theme version
    Navigate to Appearance > Themes, click on Full Frame theme, and locate the version number displayed in the theme details panel. Alternatively, inspect the style.css file in wp-content/themes/full-frame/ and find the version comment in the file header
    Affected if Version is less than 2.7.3 or less than 4.3.1
  3. Determine if user-supplied input is processed
    Review theme settings and options that accept user input (such as customizer settings, theme-specific options panels, or any custom fields) and verify if the data is rendered on pages without sanitization
    Affected if The theme processes and displays user-supplied data in HTML contexts without proper output encoding

The environment is affected if the Full Frame theme is installed with a version below 2.7.3 or below 4.3.1, and the theme processes user input that gets stored and displayed without sanitization.

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
Upgrade available Upgrade to 2.7.3 / 4.3.1 or later
Fixed in 2.7.34.3.1
Interim mitigation

Update to the latest version of the Full frame theme once a patch is released, or implement proper input sanitization and output encoding on all user-supplied data before rendering in HTML contexts.

Recommended fix High confidence

Full Frame version 2.7.3 or higher, or version 4.3.1 or higher

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins page.
  3. 3. Locate the 'Full Frame' theme/plugin from catchthemes.
  4. 4. Update the plugin to version 2.7.3 or higher, or version 4.3.1 or higher depending on your product branch.
  5. 5. Verify the update was successful by checking the installed version.
  6. 6. Test that the XSS vulnerability is no longer exploitable in affected input fields.

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

Fix this in Full Frame Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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