Wp Job PortalWordPress extension · Wpjobportal
CVE-2023-28534
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+) Stored Cross-Site Scripting (XSS) vulnerability in WP Job Portal WP Job Portal – A Complete Job Board plugin <= 2.0.0 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 confidenceAuthenticated stored XSS in WP Job Portal plugin versions 2.0.0 and below allows subscriber+ users to inject malicious JavaScript through plugin input fields, which executes when other users view the injected content in the job board interface.
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
Wp Job PortalWordPress extension
<= 2.0.0CVSS 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.
-
Check WP Job Portal plugin versionNavigate to WordPress admin > Plugins > Installed Plugins and locate 'WP Job Portal' or 'Wpjobportal Wp Job Portal'. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag.Affected if Installed version is 2.0.0 or lower
-
Verify plugin is activeIn WordPress admin > Plugins > Installed Plugins, confirm the WP Job Portal plugin shows as 'Active'. The vulnerability only applies when the plugin is actively running.Affected if Plugin is installed and active with version 2.0.0 or lower
-
Check for subscriber-level user accountsGo to WordPress admin > Users and review the role column. Look for any users assigned the 'Subscriber' role or custom roles with equivalent or higher privileges (Contributor, Author, Editor, Administrator).Affected if At least one user account with Subscriber role or higher exists in WordPress
-
Confirm job/resume submission features are accessibleVisit the frontend of the site and check if job submission forms, resume submission forms, or other input forms provided by WP Job Portal are publicly accessible or accessible to subscriber-level users.Affected if Plugin input fields (job application forms, resume uploads, etc.) are accessible to users with Subscriber role or above
-
Inspect database for suspicious stored contentQuery the WP database tables associated with WP Job Portal (typically wp_wpjobportal_job_apply, wp_wpjobportal_resume, or similar plugin tables) for any entries containing script tags, javascript:, or onload/onerror attributes.Affected if Database contains unsanitized HTML/JavaScript in plugin-related tables that could execute when viewed
User is affected if WP Job Portal plugin version 2.0.0 or lower is installed and active, and subscriber-level or higher user accounts or input fields exist in the environment.
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 WP Job Portal plugin to a version higher than 2.0.0; if no update available, implement proper input sanitization and output escaping on all user-supplied fields before rendering.
Fix this in Wp Job Portal
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28534 — 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-2023-28534 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