ActivelloWordPress extension · Colorlib
CVE-2022-45358
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 · uneditedAuth. (subscriber+) Reflected Cross-Site Scripting (XSS) vulnerability in Silkalns Activello theme <= 1.4.4 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 · high confidenceReflected Cross-Site Scripting (XSS) vulnerability in the Silkalns Activello WordPress theme allows authenticated users with subscriber-level privileges or higher to inject malicious scripts via unsanitized input. The vulnerability affects versions 1.4.4 and below.
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
ActivelloWordPress extension
<= 1.4.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Activello theme installationNavigate to wp-content/themes/ directory via FTP or file manager. Check for the presence of the 'activello' theme folder. Alternatively, in WordPress admin go to Appearance > Themes to verify Activello is installed.Affected if The activello theme folder exists in the WordPress themes directory.
-
Determine installed Activello versionOpen the style.css file located in wp-content/themes/activello/ and look for the 'Version:' header in the file comment block at the top. Alternatively, check the theme's functions.php for the version definition.Affected if The version number displayed is 1.4.4 or lower.
-
Verify WordPress user roles existLog into WordPress admin and navigate to Users > All Users. Review the list to identify any users with roles of Subscriber, Contributor, Author, Editor, or Administrator.Affected if At least one user account with Subscriber-level privileges or higher exists in the WordPress installation.
-
Check for vulnerable parameter usageInspect the theme's PHP files (particularly header.php, footer.php, or any files handling URL parameters) for usage of $_GET, $_POST, or $_REQUEST without proper sanitization functions like esc_html(), esc_attr(), or sanitize_text_field().Affected if User-supplied parameters from $_GET, $_POST, or $_REQUEST are output to HTML without sanitization.
You are affected if the Activello theme version is 1.4.4 or below and your WordPress site has at least one user with subscriber-level privileges or higher, as this provides the authentication vector required for the reflected XSS.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade the Activello theme to the latest patched version (if available) or apply input sanitization/encoding to all user-supplied parameters in the theme's PHP files to prevent script injection.
Fix this in Activello
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45358 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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