CVE-2026-24979
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in NooTheme Jobica Core jobica-core allows Reflected XSS.This issue affects Jobica Core: from n/a through <= 1.4.1.
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 confidenceReflected XSS vulnerability in NooTheme Jobica Core theme allows attackers to inject malicious JavaScript via unsanitized user input that gets reflected back in web page content. This affects all versions up to and including 1.4.1.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Jobica Core theme is installedInspect the wp-content/themes directory or check the WordPress theme management panel for the presence of the Jobica Core theme.Affected if Jobica Core theme is not installed on the WordPress site.
-
Determine the installed version of Jobica Core themeLocate the style.css file within the Jobica Core theme folder and read the version declaration in the theme header comment, or check the theme version displayed in the WordPress admin panel under Appearance > Themes.Affected if The installed version is 1.4.1 or lower.
-
Identify user input fields that reflect data back to pagesReview the theme templates and search for instances where PHP superglobals such as $_GET, $_POST, or $_REQUEST are used and echoed directly into HTML output without apparent sanitization functions.Affected if The theme contains code that reflects user-supplied parameters into page content without sanitization.
-
Test for reflected XSS in URL parametersIdentify common input points such as search parameters, sort options, or filter fields, then inject a test payload like <script>alert(1)</script> into URL parameters and observe if the payload is rendered as-is in the page response.Affected if The payload is rendered directly in the page HTML without encoding or is stripped but the underlying vulnerability remains exploitable.
The environment is affected if Jobica Core theme version 1.4.1 or lower is installed and user input is reflected into web pages without proper output encoding.
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 dataApply proper input validation and output encoding/sanitization to all user-supplied data before rendering in HTML contexts. Update to a patched version if available from the vendor.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24979 — 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-2026-24979 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