Arforms Form BuilderWordPress extension · Reputeinfosystems
CVE-2022-45838
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 · uneditedUnauth. Stored Cross-Site Scripting (XSS) vulnerability in Repute InfoSystems ARForms Form Builder plugin <= 1.5.5 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 confidenceUnauthenticated stored Cross-Site Scripting (XSS) vulnerability in ARForms Form Builder plugin versions 1.5.5 and below allows unauthenticated attackers to inject malicious JavaScript payloads through form inputs that persist on the server and execute when users view the affected form content.
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
Arforms Form BuilderWordPress extension
<= 1.5.5CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify ARForms Form Builder is installedCheck the WordPress plugins directory (wp-content/plugins) for the 'arforms-form-builder' folder, or list installed plugins via WP admin under Plugins > Installed PluginsAffected if The ARForms Form Builder plugin is present in the installation
-
Identify the installed plugin versionOpen the main plugin file (usually arforms.php or class-arforms.php in the plugin folder) and locate the version comment/constant in the file header, or check the plugin details in WordPress admin Plugins pageAffected if The version number is 1.5.5 or lower
-
Confirm unauthenticated form submissions are enabledCheck if forms created with ARForms are configured to accept submissions without requiring user authentication. This can be verified by examining form settings in ARForms editor or reviewing the frontend form submission endpointAffected if Public (non-logged-in) users can submit forms without any authentication requirement
-
Inspect stored form submissions for malicious contentAccess ARForms entries/submissions in WordPress admin (ARForms > Entries) and review submitted data for any unsanitized script tags, javascript: URLs, or event handler attributes in form fieldsAffected if Any stored form submissions contain raw HTML/script tags without sanitization or encoded output
If ARForms Form Builder version 1.5.5 or lower is installed AND accepts unauthenticated form submissions, the environment is likely affected by this stored XSS vulnerability.
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 dataUpdate ARForms Form Builder to the latest patched version and audit all form input handling for proper sanitization and output encoding.
Fix this in Arforms Form Builder
Scoped from the published advisory
- 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-2022-45838 — 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-45838 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