dbcve.org
Apollo13 Framework ExtensionsWordPress extension · Apollo13themes

CVE-2023-47190

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-08
Fix available
A fix is available. Upgrade to after 1.9.0 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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Apollo13Themes Apollo13 Framework Extensions plugin <= 1.9.0 versions.

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 Apollo13Themes Apollo13 Framework Extensions plugin allows authenticated users with contributor-level or higher permissions to inject malicious JavaScript through plugin input fields, which gets stored and executed when other users view affected content.

MitigationUpdate the Apollo13 Framework Extensions plugin to a version newer than 1.9.0; alternatively, restrict contributor-level user permissions and implement output sanitization on all user inputs within the plugin until a patch is available.

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
Apollo13 Framework ExtensionsWordPress extension
Affected:<= 1.9.0

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. Verify Apollo13 Framework Extensions plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'apollo13-framework-extensions' or similar. Check if the plugin appears in the list.
    Affected if The plugin is present and active in the WordPress installation.
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Apollo13 Framework Extensions' or 'Apollo13themes Apollo13 Framework Extensions'. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for a Version header comment.
    Affected if The installed version is 1.9.0 or lower.
  3. Confirm WordPress user roles with contributor-level access
    Navigate to WordPress admin > Users > All Users. Review the role assigned to each user account. Contributor role and higher (Author, Editor, Administrator) have the capability to access plugin input fields.
    Affected if At least one user account has Contributor, Author, Editor, or Administrator role.
  4. Inspect plugin input fields for lack of sanitization
    Locate the plugin settings page in WordPress admin (typically under Theme Options, Framework, or a dedicated Apollo13 menu). Examine any text input fields, textarea fields, or option fields provided by the plugin. Check if the values are output without apparent sanitization by viewing the page source.
    Affected if Plugin input fields accept user-supplied text and display it without visible output encoding or sanitization notices.

You are affected if the Apollo13 Framework Extensions plugin is installed with version 1.9.0 or lower and your WordPress site has at least one user with Contributor-level permissions or higher.

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 a release after 1.9.0
Interim mitigation

Update the Apollo13 Framework Extensions plugin to a version newer than 1.9.0; alternatively, restrict contributor-level user permissions and implement output sanitization on all user inputs within the plugin until a patch is available.

Recommended fix Moderate confidence

1.9.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Apollo13 Framework Extensions plugin
  4. Check the current version number
  5. If the installed version is 1.9.0 or below, click 'Update Now' to update to the latest version
  6. Verify the update completes successfully
  7. Test the affected functionality to confirm the XSS vulnerability is no longer present

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

Fix this in Apollo13 Framework Extensions 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-47190 — 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-47190 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