CVE-2024-11853 json
jAlbum Bridge <= 2.0.16 - Authenticated (Contributor+) Stored Cross-Site Scripting via ar Parameter
published 2024-12-03 23 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-34217
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
The jAlbum Bridge plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘ar’ parameter in all versions up to, and including, 2.0.16 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. It was determined that the patch in 2.0.16 was insufficient, and 2.0.17 is considered the fully patched version.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- mlaza jAlbum Bridge
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/72b50c83-7128-4e38-9a5e-0954928ff002?source=cve
- plugins.trac.wordpress.org /browser/jalbum-bridge/tags/2.0.15/jalbum-bridge.php#L41
- wordpress.org /plugins/jalbum-bridge/#developers
- plugins.trac.wordpress.org /changeset/3198794/
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3227528%40jalbum-bridge&new=3227528%40jalbum-bridge&sfp_email=&
Sources
- CVE List CVE-2024-11853
- NVD CVE-2024-11853
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.