Tag: SQL injection

  • Oxygen 6.2.2 Security Update Patches SQL Injection and XSS (2026)

    Oxygen 6.2.2 Security Update Patches SQL Injection and XSS (2026)

    Takeaway: On November 16, 2026, Oxygen Builder released Oxygen 6.2.2, a security update that fixes an SQL injection and cross-site scripting issue. The vendor says the issue would let an attacker take over a site if a logged-in administrator clicked on a malicious link. Oxygen says it discovered the issue in an internal security audit, not from a third-party report, and tells site owners to update immediately.

    This is a short official notice, and it is aimed at people who already run Oxygen on a WordPress site. If that is you, the action is straightforward: install 6.2.2 and confirm the running version before you move on to other work. The post does not offer a temporary workaround, a CVE identifier, or a list of older versions that are out of scope.

    What Oxygen published

    The November 16 release note, written by Elias Lista, is titled “Oxygen 6.2.2 – Security Update.” In a few sentences it states three facts that matter for operators:

    • The release fixes an SQL injection and a cross-site scripting issue.
    • The described impact is site takeover if a logged-in administrator clicks a malicious link.
    • The company found the issue during an internal security audit. It was not reported by a third party.

    That last point is useful context, not a reason to delay. An internally found bug can still be abused once a patch is public, because the patch itself tells defenders — and anyone watching plugin updates — that a serious issue existed in earlier builds. Oxygen’s own recommendation is to update immediately.

    What the notice does not say

    The official post is a one-minute read. It does not assign a CVE number, name a CVSS score, or list the exact earlier versions that are affected. It also does not say whether Oxygen Classic, add-ons, or a specific PHP or WordPress version are part of the issue. We are not filling those gaps from unofficial write-ups.

    The practical reading is conservative. If a site still runs Oxygen at a version below 6.2.2, treat it as in scope until you have installed this release and confirmed the version on that site. If you maintain staging and production copies, update both, and do not assume a patched staging site means production is safe.

    Who should update, and how

    Anyone running Oxygen on a WordPress site should install 6.2.2. The impact Oxygen describes depends on a logged-in administrator following a malicious link, which is a common real-world path: a phishing message, a compromised dashboard notice, or a link in a comment or support thread. Reducing the number of administrator accounts and being careful with unexpected links is good hygiene, but it is not a substitute for the vendor patch.

    Install the update through your usual WordPress plugin updates, or from the source you already use for Oxygen releases. After the update, confirm that the active Oxygen version is 6.2.2. If you use object caching or a page cache, clear it after the update so you are not looking at a stale admin screen. The release note does not describe a required database migration or a theme rebuild; it is presented as a security release you should apply now.

    This sits in the same operational bucket as other recent WordPress security work, including our note on the WordPress 7.1.4 upgrade-race attacks: when a vendor ships a security release and tells you to update immediately, the patch is the fix. Waiting for a public exploit write-up is the wrong order of operations.

    ItemWhat the official notice says
    ReleaseOxygen 6.2.2, published November 16, 2026
    Vendor postOxygen 6.2.2 – Security Update (Elias Lista)
    Issues fixedSQL injection and cross-site scripting
    Stated impactSite takeover if a logged-in administrator clicks a malicious link
    DiscoveryInternal security audit; not reported by a third party
    Vendor adviceUpdate immediately
    CVE / version rangeNot stated in the official note

    FAQ

    What is Oxygen 6.2.2?

    It is a security release of the Oxygen WordPress builder, published on November 16, 2026. Oxygen describes it as a fix for an SQL injection and cross-site scripting issue and tells site owners to update immediately.

    How serious is the issue?

    According to the vendor, a successful attack could take over a site if a logged-in administrator clicked a malicious link. Oxygen does not publish a CVSS score in the release note. The recommended response is still to install 6.2.2 now.

    Was this reported by an outside researcher?

    No. Oxygen says it discovered the issue during an internal security audit and that it was not reported by a third party.

    Which earlier versions are affected?

    The official note does not list a version range. If you run Oxygen at a version below 6.2.2, update and confirm the running version on that site.

    Is there a CVE number?

    The official release note does not assign or mention a CVE identifier.

    How do I update?

    Use your usual WordPress plugin update process, or the channel you already use for Oxygen releases. Afterward, confirm that the active version is 6.2.2. The vendor post does not describe an alternative mitigation.

    Does a cache plugin need to be cleared?

    The official note does not mention caches. Clearing object and page caches after a plugin security update is still a sensible check, so you are confirming the new version against a fresh admin view.

    Is updating enough, or do I also need to change administrator habits?

    The patch is the fix Oxygen is shipping. The described attack path involves a logged-in administrator clicking a malicious link, so limiting administrator accounts and treating unexpected links with caution remains useful. Those steps do not replace installing 6.2.2.