OxygenWordPress extension · Soflyy
CVE-2022-46841
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Soflyy Oxygen Builder plugin <= 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 · moderate confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the Soflyy Oxygen Builder WordPress plugin affecting versions 4.4 and earlier. CSRF attacks trick authenticated users into unknowingly submitting malicious requests to the application, potentially allowing attackers to perform unauthorized actions with the privileges of the logged-in user.
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
OxygenWordPress extension
< 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Locate Oxygen Builder pluginIn WordPress admin, go to Plugins > Installed Plugins and look for 'Oxygen Builder' or 'Oxygen' in the list. Note whether it is activated.Affected if Oxygen Builder plugin is installed and active in WordPress
-
Find installed Oxygen versionIn WordPress admin, go to Oxygen > About or Plugins page and locate the version number displayed next to the plugin name.Affected if The displayed version number is lower than 4.4 (e.g., 4.3, 4.2, 3.x, etc.)
-
Confirm WordPress user authentication is enabledCheck WordPress admin > Settings > General to see if 'Membership' allows user registration, or check if the site has any user accounts beyond the administrator.Affected if The site allows registered users (any role) to log in, making CSRF attacks possible
-
Inspect HTTP response headers for referer validationUse browser dev tools or curl -I to examine HTTP responses from the site and check if 'Referrer-Policy' headers are present and strict.Affected if No referrer validation is implemented and the site uses vulnerable Oxygen version
You are affected if Oxygen Builder version 4.4 or earlier is installed on your WordPress site and the site has authenticated users able to perform state-changing actions.
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.
dbcve · scoped4.4
Update Oxygen Builder to the latest version which should contain CSRF protection mechanisms. If an update is unavailable, implement anti-CSRF tokens (nonces) on state-changing operations and validate request referrers.
Oxygen Builder 4.4 or later
- 1. Log in to your WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the Oxygen Builder plugin
- 4. If an update is available, click 'Update Now' to update to the latest version (4.4 or later)
- 5. Verify the update completed successfully
- 6. Test that the Oxygen Builder functionality works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Oxygen
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46841 — 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-46841 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